IIRC, an unlimited memory_limit isn't supported by the CLI (I'll try to find a source for this) but for now, try passing it into the command:
php -d memory_limit=128M my_script.php
Apparently I was dreaming about the unlimited memory_limit not being supported for php cli. Regardless, it looks like the value from the ini is ignored. The simplest ...
su - username is interpreted by your su to mean "run username's shell as an interactive login shell"
su username - is interpreted by your su to mean "run the following non-interactive command (-) as username"
the latter only worked at all because:
your su passes trailing arguments to sh for parsing
sh takes - to mean "run as a login shell (read /etc/profile,...
There is an lsb-release package that supplies the lsb_release command. This is separate from the lsb, lsb-base, and lsb-core packages. None of the lsb packages are essential. So if your package needs lsb_release it should specify that it depends on lsb-release.
Upgrade all packages:
apt-get update; apt-get upgrade;
If you want to upgrade just one package (e.g. php5):
apt-get update; apt-get install php5;
For the package versions available on Debian take a look at:
If you want to install php5 5.4.4-2, that is only available on wheezy, you should add wheezy to your /etc/...
You don't tell logrotate which file to rotate on the command line. You pass it a configuration file. So in your case, logrotate is reading /var/log/syslog and trying to parse it as a config file and failing (hence your errors).
If you want to rotate /var/log/syslog it needs to be listed in a logrotate config file somewhere, and you just run logrotate. If ...
Sounds very much like the drives are doing SMART scrubbing (automatic offline testing).
smartctl -a /dev/hdx
should confirm the configuration with:
Auto Offline Data Collection: Enabled.
smartctl --offlineauto=off /dev/hdx
It could be something else too...
One consequence of removing the MTA is that mail generated by the system itself (usually sent to root), for example by Cron, Logwatch, rkhunter and others cannot be be delivered.
So yes, an MTA is an integral part of any Unix-like system and I doubt Debian will let you uninstall the MTA without complaining and suggesting an alternative. But it's not a big ...
First of all, they are only warnings, not errors.
Warning: The modules file '/proc/modules' is missing.
rkhunter is trying to check the kernel modules, but it cannot because the file /proc/modules doesn't exist. You can disable the test by changing the below line:
DISABLE_TESTS="suspscan hidden_procs deleted_files packet_cap_apps"
I haven't tested this, but I believe that after you run your dpkg-reconfigure on an example machine, you can run debconf-get-selections | egrep "^gitolite\s" to get what was set. (it's in the debconf-utils package if you don't have it).
Then on the CLI, debconf-set-selections $FILENAME before running apt.
Then with puppet it would be something like:
Have you checked this parameter: @local_domains_acl
It is defined on /etc/amavis/conf.d/05-domain_id. According to the Amavisd-new documentaion
No spam-related headers inserted? Here are some reasons:
@local_domains_acl is not correctly set. These headers are only
inserted for recipients matching @local_domains_acl ...
Pinning is going to put you in dependency hell, as @Juan noticed.
When I want the bleeding edge on my Debian systems I usually turn to http://www.dotdeb.org/
For proper instructions ->
apt-get install ntp. If you've never had it installed before, you should be good to go. If you have, and therefore, might have stale config files, you could apt-get remove --purge ntp and apt-get install ntp again to get new config files. Or if you want to keep your config files, I recommend checking that /etc/default/ntp has NTPD_OPTS='-g'. This says to ...
it appears that /usr/local and /usr/local/bin (both of which are owned by root:staff) are group-writable by default on Debian Squeeze.
This is, at present, by design, you may review the team's missives on the purpose/importance of this choice in the following thread: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538392
Is there a reason that they ...
supervise is a lightweight, efficient alternative. Under debian it is packaged in daemontools. You can also read this related question, which lists some supervise criticisms, and mentions restartd as another possibility.
Finally, if you want something incredibly easy to setup, I've had great success with monit. It is also packaged in Debian.
I had a similar issue but crontab was working and for some of the log directories logrotate worked but for some it didn't. When I tried to run the logrotate manually, I got some error messages.
user@server:/var/log/apache2$ sudo /usr/sbin/logrotate -f /etc/logrotate.conf
error: error creating output file /var/log/apache2/access.log.1.gz: File exists
First, I must ask: "shutdowns"? Do you mean that the machine reboots or does it actually halt? If it halts, it is either misconfigured (perhaps in BIOS) or something is actively shutting down the machine (i.e. init 0).
If not, your primary candidate would be /var/log/syslog and /var/log/kern.log as your problem sounds like a kernel panic or a software-...
What you're seeing is a stack trace. It's an un-handled error from the kernel showing the path of execution when something goes so damn wrong that there's nothing else in place to do except log the problem and leave it for a human to figure out.
The call at the head is usually the defining one:
WARNING: at /build/buildd-linux-2.6_2.6.32-45-amd64-FcX7RM/...
It is exactly what is says on the tin. Your DN cn=myuser,dc=mydomain,dc=com does not have enough permissions to modify the cn=config tree. And when you are trying "to specify the config database" you are using an entirely different DN, cn=myuser,cn=config, which apparently either doesn't exist or you are using a wrong password.
To do modifications like ...
You're on an OpenVZ (container) based virtual machine. As a result you have no control over the kernel; it is provided by your hosting provider, and you are limited to whatever the provider chooses to provide.
If you want a different kernel, you either need to contact your hosting provider, or use something other than OpenVZ.
sudo apt-get purge locales
sudo aptitude install locales
and the famous:
sudo dpkg-reconfigure locales
This rids the system of locales, then re-installs locales and downgrades libc6 from 2.19 to 2.13 which is the issue. Then configures locales again.
Is dhcpcd/dhclient still running? It will refresh its DHCP address on the interface if you don't kill it.
Also, did you configure Network Manager? That'll override the interfaces file. Get rid of it if you're not using it.
Check that your logrotate is being run by cron.
From the comment discussion - it appears that cron is not working correctly. I had a cronjob in my crontab without user but this only come to light when I restarted the cron daemon
My ubuntu and centos systems have an /etc/cron.daily/logrotate file the contents of which are
test -x /usr/...
When your primary isn't available, the foreign mailserver queues mails und does a delivery retry up to five days.
I haven`t setup an additional MX, because most spammers deliver to the secondary first. Often this server isn't maintained as good as the primary.
summa summarum: much work, less benefit. Let the world queue your mails!
You've probably stumbled into a 32-bit/64-bit problem. Disks with the MBR partitioning layout are limited to a 2TB maximum drive size due to the field widths in the partition table and the block-size; the field is 32-bits wide, but with a 512 block-size 2TB is as big as it allows. You can get higher with 4K-block devices, but those don't appear to be used in ...