Tag Info

Hot answers tagged

4

Found the problem. The base AMI on EC2 for Debian Jessie, does not have dbus installed. hostnamectl seems to need dbus. So the fix is to: apt-get update && apt-get install -y dbus And then: echo "myhostname" > /etc/hostname echo "127.0.0.1 myhostname" >> /etc/hosts hostnamectl set-hostname myhostname This worked.


4

Sounds like (a) root's crontab is initially empty and (b) the -e option is set in the shell. If the user's crontab file is empty then crontab -l exits with status 1. If shell is running with -e option then it will exit immediately on failure (defined as exiting with non-zero status). Look for errexit in the output of echo $SHELLOPTS to check for this ...


3

When you declare the haproxy class you can require it, e.g.: class { 'haproxy': require => Apt::Source['debian_wheezy'], }


2

You need to install Grub2 on both disks. Try to run grub2-install /dev/sda; grub2-install /dev/sdb (or similar; check you grub man page for more information). EDIT: after reading better your post, I think Grub2 is not the culprit here, as it seems that your system correctly load the required kernel. Try to substitute the UUID with the /dev/ entry pointing ...


1

it would be nice to know what commands broke your replication, but I suppose, the mysql_upgrade script would be that rogue. If yes, you can rebuild the mysql package, adding to the post install script a --skip-write-binlog (this is not needed after 5.6.7) But normally I never would just apt-get upgrade a server which is in production, stop the slave, ...


1

I don't get the requirement of "one host at a time". Puppet is perfectly capable of serving and recording multiple puppet agent runs at a time. Just to rule out that it's an environment issue, run sudo -i <command>. Anyway, using Puppet in push mode might be more fitting to your demands. The puppet agent (which you need to reconfigure first) will ...


1

In mail architecture like above, you need synchronize two configuration The format* and location of where postfix stores the incoming email The format* and location of where dovecot retrieves the email When they are out of sync, dovecot won't find email that previously stored by postfix. The related dovecot parameter is mail_location = ...


1

Check you gave execution right to your script #chmod +x hostname.sh Why don't you use the DHCP option 12 instead? https://tools.ietf.org/html/rfc1533 3.14. Host Name Option This option specifies the name of the client. The name may or may not be qualified with the local domain name (see section 3.17 for the preferred way to retrieve the domain ...


1

None of those modules set off any alarm bells for me. I wouldn't expect them to do much to the default behavior of nginx until you reference them from the nginx config and use them for something.


1

I was able to solve the problem by clearing the certs of all of the nodes out of the master,as well as the master cert and fulling deleting the SSL directory off the agent. I had cleared the agents before but it seemed clearing the master one was required as well.



Only top voted, non community-wiki answers of a minimum length are eligible