I have been having a weird problem with Zimbra(7.1.4_GA_2555.DEBIAN5) lately:

On the (web)control panel the status keep changing to red every few days. When this is happens the output of zmcontrol status still shows running:
antispam Running
antivirus Running
imapproxy Running
ldap Running
logger Running
mailbox Running
memcached Running
mta Running
snmp Running
spell Running
stats Running
zmconfigd Running

Every thing runs fine except automated mail forwarding from one account to another(which is critical for us).

I have been through Zimbra forums and the following ALWAYS fixes the issue:

su – zimbra -c “zmprov mcf zimbraLogHostname mail.mydomain.com”

/opt/zimbra/libexec/zmsyslogsetup

/etc/init.d/rsyslog restart

su – zimbra -c “zmcontrol restart”

After I run the above commands, the status on control panel turns green and mail forwarding starts to work again BUT only for a few days.

Other than the above, everything works fine including Server statistics.

Anyone seen this issue before?

I was able to fix this issue after going through the following link:

http://www.zimbra.com/forums/installation/34359-upgrade-6-0-2-stats-status-no-longer-working-6.html

since my system is using rsyslog instead of standard syslog it will never reload the syslog-deamon and therefore you have problems with the logfiles. This is even more problematic as zimbra begins with z and therefore it is the last script which gets executed from logrotate, if it would not be the last one, there would have been a chance that a later script reloads the syslog daemon I changed this line to:

killall -HUP rsyslogd 2> /dev/null || true

(notice the r in front of rsyslogd)

Check more discussion of this question.

I am running an ISPConfig3 server with Lenny which I want to upgrade the Squeeze, however… I am not at the terminal and the server is in my server-hall.

Can I upgrade Lenny to Squeeze over SSH? I checked the update list and both openssh-client & openssh-server are being kept back… however, I feel unsure to if I can and should proceed.

This is what apt-get shows me when running apt-get upgrade:

The following packages have been kept back:
  amavisd-new apache2 apache2-mpm-prefork apache2.2-common apt apt-listchanges apt-utils aptitude autoconf automake avahi-daemon bash
  bc bind9-host binutils build-essential courier-maildrop cpio cpp cpp-4.3 cron dbus dc debianutils dhcp3-client dhcp3-common diff
  djvulibre-desktop dnsutils dpkg dpkg-dev e2fsprogs ed enscript expect findutils flex ftp g++ g++-4.3 gcc gcc-4.3 gcc-4.3-base
  gettext ghostscript gnupg gpgv grep grub grub-common html2text imagemagick info iptables ispell libaprutil1 libarchive-zip-perl
  libberkeleydb-perl libc6 libc6-dev libc6-i386 libcompress-raw-zlib-perl libcompress-zlib-perl libconvert-uulib-perl libcups2
  libcupsimage2 libcurl3 libdatetime-locale-perl libdatetime-perl libdbd-mysql-perl libdbi-perl libdevmapper1.02.1
  libdigest-sha1-perl libdjvulibre21 libedit2 libgcc1 libgdbm3 libglib2.0-0 libglib2.0-data libgomp1 libgs8 libgsf-1-114 libgtk2.0-0
  libgtk2.0-bin libhtml-parser-perl libio-compress-base-perl libio-compress-zlib-perl libkrb53 liblocale-gettext-perl
  libmail-box-perl libneon27 libneon27-gnutls libnet-dns-perl libnet-libidn-perl libnet-ssleay-perl libnetaddr-ip-perl libpango1.0-0
  libparams-validate-perl libpq5 librsvg2-2 libsasl2-2 libsasl2-modules libsasl2-modules-sql libsocket6-perl libstdc++6
  libstdc++6-4.3-dev libsvn1 libthai-data libthai0 libtool libts-0.0-0 libwv-1.2-3 libx11-6 libxcb1 libxi6 linux-image-2.6-amd64
  locales m4 man-db mc memcached mutt mysql-client nano nfs-common ntp ntpdate openssh-client openssh-server perl perl-base
  perl-modules polipo postfix postfix-mysql python python-apt python-minimal python-sqlalchemy python2.5 python2.5-minimal quota
  readline-common reportbug rpm sasl2-bin sed source-highlight subversion sysv-rc tor tor-geoipdb udev unixodbc util-linux wget wv
The following packages will be upgraded:
  acpi-support-base acpid adduser apache2-doc apache2-suexec apache2-utils apticron arj aspell aspell-de aspell-en aspell-fi
  aspell-fr aspell-nl aspell-ru aspell-sv at automake1.9 autotools-dev base-files base-passwd bash-completion bison bsd-mailx
  bsdmainutils bsdutils busybox bzip2 ca-certificates cabextract clamav clamav-base clamav-daemon clamav-docs clamav-freshclam
  clamav-testfiles console-common console-data console-tools coreutils courier-authdaemon courier-authlib courier-authlib-mysql
  courier-authlib-userdb courier-base courier-imap courier-imap-ssl courier-pop courier-pop-ssl courier-ssl curl daemon db4.6-util
  dbus-x11 debconf debconf-i18n debhelper debian-archive-keyring debian-faq defoma dictionaries-common dmidecode doc-debian e2fslibs
  eject fail2ban fakeroot fam file firmware-bnx2 fontconfig fontconfig-config gawk getmail4 gettext-base groff-base gs-common gsfonts
  gzip hicolor-icon-theme hostname iamerican ibritish ifupdown initramfs-tools initscripts installation-report iproute iputils-ping
  java-common klibc-utils laptop-detect less libacl1 libaio1 libapache2-mod-fcgid libapache2-mod-jk libapr1 libasound2 libaspell15
  libatk1.0-0 libatk1.0-data libattr1 libauthen-sasl-perl libavahi-common-data libavahi-common3 libblkid1 libbz2-1.0 libcairo2
  libcap2 libclamav6 libclass-singleton-perl libcomerr2 libconsole libconvert-asn1-perl libconvert-tnef-perl libcroco3 libcwidget3
  libdaemon0 libdatetime-timezone-perl libdb4.6 libdb4.8 libdbus-1-3 libdigest-hmac-perl libexpat1 libfam0
  libfile-copy-recursive-perl libfile-remove-perl libfontconfig1 libfontenc1 libfreetype6 libgc1c2 libgcrypt11 libgd2-xpm
  libgeoip-dev libgeoip1 libgmp3c2 libgnutls26 libgpg-error0 libgpm2 libgsf-1-common libgssglue1 libgtk2.0-common
  libhtml-template-perl libhtml-tree-perl libice6 libidn11 libilmbase6 libio-multiplex-perl libio-socket-inet6-perl
  libio-socket-ssl-perl libipc-run3-perl libjasper1 libjpeg62 libkeyutils1 libklibc liblcms1 libldap-2.4-2 liblockfile1 liblqr-1-0
  libltdl7 liblzo2-2 libmagic-dev libmagic1 libmail-sendmail-perl libmail-spf-perl libmailtools-perl libmcrypt4 libmhash2
  libmime-tools-perl libmime-types-perl libncurses5 libncursesw5 libnet-cidr-perl libnet-daemon-perl libnet-ident-perl
  libnet-ldap-perl libnewt0.52 libnfsidmap2 libnss-mdns libobject-realize-later-perl libopenexr6 libpam-modules libpam-mysql
  libpam-runtime libpam0g libpango1.0-common libpaper-utils libpaper1 libpci3 libpcre3 libpixman-1-0 libplrpc-perl libpng12-0
  libpopt0 libqdbm14 libreadline5 librpcsecgss3 libselinux1 libsepol1 libserf-0-0 libsigc++-2.0-0c2a libslang2 libsm6 libsqlite0
  libsqlite3-0 libss2 libssh2-1 libssl-dev libssl0.9.8 libsysfs2 libt1-5 libtasn1-3 libtext-charwidth-perl libtext-iconv-perl
  libtext-wrapi18n-perl libtidy-0.99-0 libtiff4 libtimedate-perl libtommath0 liburi-perl libusb-0.1-4 libuser-identity-perl libuuid1
  libwmf0.2-7 libwrap0 libwww-perl libx11-data libxau6 libxcb-render-util0 libxcb-render0 libxcomposite1 libxcursor1 libxdamage1
  libxdmcp6 libxext6 libxfixes3 libxfont1 libxft2 libxinerama1 libxml2 libxml2-dev libxmuu1 libxpm4 libxrandr2 libxrender1 libxt6
  libxtst6 linux-libc-dev lockfile-progs login logrotate lsb-base lsb-release lsof make makedev manpages mawk mcrypt mdadm mercurial
  mercurial-common mime-support mktemp mlocate mlock module-init-tools mount ncurses-base ncurses-bin ncurses-term net-tools netbase
  nomarch openbsd-inetd openssl openssl-blacklist passwd patch pciutils po-debconf portmap postfix-doc procmail procps psfontmgr
  psmisc pure-ftpd-common pure-ftpd-mysql python-beaker python-central python-support quotatool rcs rkhunter rsyslog shtool socat
  spamassassin spamc ssh ssl-cert sun-java6-bin sun-java6-jdk sun-java6-jre sysstat sysvinit sysvinit-utils tar tasksel tasksel-data
  tcl8.4 tcpd texinfo time traceroute ttf-dejavu ttf-dejavu-core ttf-dejavu-extra tzdata ucf unhide unrtf unzip update-inetd usbutils
  vim-common vim-tiny w3m wamerican webalizer whiptail whois x-ttcidfont-conf x11-common xauth xfonts-encodings xfonts-utils zip
  zlib1g zlib1g-dev zoo
343 upgraded, 0 newly installed, 0 to remove and 157 not upgraded.

Can I do the upgrade? Is there anything then will kill my SSH connection? Can I run it otherwise in the background so the upgrade process continues even-though the SSH connect might have been killed?

That’s why God invented the KVM over IP.

In my experience, I wouldn’t do it if it’s not absolutely necessary. If you can wait and do it after the weekend, I wouldn’t take the risk.

I’ve done multiple lenny to squeeze upgrades and in about 30 machines, I had only one that didn’t turn out well. So it’s for you to decide if you can take the risk or not. Normally these upgrades go smoothly. Do note that you will need to reboot the machine to complete the upgrade, so you will loose ssh connection anyway.

Normally you will not loose SSH when doing a dist-upgrade from lenny to squeeze.

Check more discussion of this question.

Here is my /etc/apt/sources.list

###### Debian Main Repos
deb http://ftp.us.debian.org/debian/ lenny main contrib non-free###### Debian Update Repos
deb http://security.debian.org/ lenny/updates main contrib non-free
deb http://ftp.us.debian.org/debian/ lenny-proposed-updates main contrib non-free

When I do:

# apt-get update

I’m getting some good lines, then:

Err http://ftp.us.debian.org lenny/contrib Packages
  404 Not Found [IP: 35.9.37.225 80]
Err http://ftp.us.debian.org lenny/non-free Packages
  404 Not Found [IP: 35.9.37.225 80]
Err http://ftp.us.debian.org lenny-proposed-updates/main Packages
  404 Not Found [IP: 35.9.37.225 80]
Err http://ftp.us.debian.org lenny-proposed-updates/contrib Packages
  404 Not Found [IP: 35.9.37.225 80]
Err http://ftp.us.debian.org lenny-proposed-updates/non-free Packages
  404 Not Found [IP: 35.9.37.225 80]
Err http://ftp.us.debian.org lenny/main Packages
  404 Not Found [IP: 35.9.37.225 80]
W: Failed to fetch http://security.debian.org/dists/lenny/updates/main/binary-i386/Packages  404 Not Found [IP: 149.20.20.6 80]    
W: Failed to fetch http://security.debian.org/dists/lenny/updates/contrib/binary-i386/Packages  404 Not Found [IP: 149.20.20.6 80]    
W: Failed to fetch http://security.debian.org/dists/lenny/updates/non-free/binary-i386/Packages  404 Not Found [IP: 149.20.20.6 80]    
W: Failed to fetch http://ftp.us.debian.org/debian/dists/lenny/contrib/binary-i386/Packages  404 Not Found [IP: 35.9.37.225 80]    
W: Failed to fetch http://ftp.us.debian.org/debian/dists/lenny/non-free/binary-i386/Packages  404 Not Found [IP: 35.9.37.225 80]    
W: Failed to fetch http://ftp.us.debian.org/debian/dists/lenny-proposed-updates/main/binary-i386/Packages  404 Not Found [IP: 35.9.37.225 80]    
W: Failed to fetch http://ftp.us.debian.org/debian/dists/lenny-proposed-updates/contrib/binary-i386/Packages  404 Not Found [IP: 35.9.37.225 80]    
W: Failed to fetch http://ftp.us.debian.org/debian/dists/lenny-proposed-updates/non-free/binary-i386/Packages  404 Not Found [IP: 35.9.37.225 80]    
W: Failed to fetch http://ftp.us.debian.org/debian/dists/lenny/main/binary-i386/Packages  404 Not Found [IP: 35.9.37.225 80]    
E: Some index files failed to download, they have been ignored, or old ones used instead.

Now what?

From a little poking around, it appears to be a problem with the Debian mirrors. According to the mirror info, lenny should be available, although you might need to change each instance of ‘lenny’ with ‘oldstable’ in /etc/apt/sources.list. However, pulling up 3 mirrors have all shown that ‘lenny’ and ‘oldstable’ are no longer listed.

Update: I did a little more poking around, and found that the USC Mirror looks to still have ‘lenny’ listed. Comment out your existing entries in sources.list and duplicate them the:

deb http://ftp.us.debian.org/debian/

Replaced with:

deb ftp://mirrors.usc.edu/pub/linux/distributions/debian/

See if that does the trick.

With a little luck this is a temporary issue, and will resolve itself in a few days.

Update 2: It looks like this is likely temporary, and http://archive.debian.org is the best place to pull packages for Lenny. Also, it looks like security support for Lenny was ended on Feb. 12th 2012, although they did release 5.0.10, a point update, on March 10th, 2012.

It would probably be worth planning out an upgrade, especially for any Internet/public facing servers.

Check more discussion of this question.

For the past few days, I couldn’t update our apt-sources on Debian 5.0 (lenny). I get the following errors.

W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/main/binary-amd64/Packages  404 Not Found [IP: 130.89.148.12 80]W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/contrib/binary-amd64/Packages  404 Not Found [IP: 130.89.148.12 80]W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/non-free/binary-amd64/Packages  404 Not Found [IP: 130.89.148.12 80]W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/main/source/Sources  404 Not Found [IP: 130.89.148.12 80]W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/contrib/source/Sources  404 Not Found [IP: 130.89.148.12 80]W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/non-free/source/Sources  404 Not Found [IP: 130.89.148.12 80]

How do I fix this problem?

Edit:

My current sources are:

# Debian Lenny
deb http://ftp.de.debian.org/debian/ lenny main non-free contrib  
deb-src http://ftp.de.debian.org/debian/ lenny main non-free contrib  # Debian Lenny Non-US
deb http://non-us.debian.org/debian-non-US lenny/non-US main contrib non-free  
deb-src http://non-us.debian.org/debian-non-US lenny/non-US main contrib non-free# Debian Lenny Security
deb http://security.debian.org/ lenny/updates main contrib non-free

lenny is superseded by squeeze, and its lifecycle ended on Feb. 6th this year. You’ll get no updates from the core Debian community for lenny.

Options:

1. Upgrade to squeeze.
2. Stay with lenny, remove the Debian FTP servers from sources.list and keep the packages as they are. There will be no security updates.
3. Pin (man apt_preferences) necessary packages down to lenny and perform a partial upgrade, or pin all packages down to lenny and perform upgrades as needed. Leaves you with a partial system, and you are likely to get all kinds of errors, but might be necessary if neither upgrade nor keep-as-is are options.

Check more discussion of this question.

since a few days i can’t update our apt-sources on debian lenny. i get the following errors:

W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/main/binary-amd64/Packages  404 Not Found [IP: 130.89.148.12 80]W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/contrib/binary-amd64/Packages  404 Not Found [IP: 130.89.148.12 80]W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/non-free/binary-amd64/Packages  404 Not Found [IP: 130.89.148.12 80]W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/main/source/Sources  404 Not Found [IP: 130.89.148.12 80]W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/contrib/source/Sources  404 Not Found [IP: 130.89.148.12 80]W: Failed to fetch http://ftp.debian.org/debian/dists/lenny/non-free/source/Sources  404 Not Found [IP: 130.89.148.12 80]

any advice here?

thanks!

edit:

my current sources are

# Debian Lenny
deb http://ftp.de.debian.org/debian/ lenny main non-free contrib  
deb-src http://ftp.de.debian.org/debian/ lenny main non-free contrib  # Debian Lenny Non-US
deb http://non-us.debian.org/debian-non-US lenny/non-US main contrib non-free  
deb-src http://non-us.debian.org/debian-non-US lenny/non-US main contrib non-free# Debian Lenny Security
deb http://security.debian.org/ lenny/updates main contrib non-free

lenny is superseded by squeeze, and its lifecycle ended on Feb. 6th this year. You’ll get no updates from the core Debian community for lenny.

Options:

1. Upgrade to squeeze.
2. Stay with lenny, remove the Debian FTP servers from sources.list and keep the packages as they are. There will be no security updates.
3. Pin (man apt_preferences) necessary packages down to lenny and perform a partial upgrade, or pin all packages down to lenny and perform upgrades as needed. Leaves you with a partial system, and you are likely to get all kinds of errors, but might be necessary if neither upgrade nor keep-as-is are options.

Check more discussion of this question.

I’m configuring Debian 5 to run my Django app. The required application is required incompatible with Python 2.5 packages. I installed Python 2.7 and created the symlink python -> /usr/bin/python2.7/bin/python. After I installed mod_wsgi ./configure --with-python=/usr/bin/python2.7/bin/python and added to httpd.conf WSGIPythonHome /usr/bin/python2.7/bin/python.
Now I have a couple of problems. At first – after I manually installed setuptools and pip, at calling pip install -r requirements.txt of I have got an error:

raceback (most recent call last):
File “/usr/bin/pip”, line 5, in
from pkg_resources import load_entry_point
File “build/bdist.linux-i686/egg/pkg_resources.py”, line 2607, in
File “build/bdist.linux-i686/egg/pkg_resources.py”, line 565, in resolve
pkg_resources.DistributionNotFound: pip==1.0.2

How to fix the DistributionNotFound problem?

At second: in the system was installed mod_wsgi via apt-get, I manually compiled mod_wsgi 2.5 with configure flag without removing of existing version.

The app is not fire up now, how to check, as mod_wsgi works right?

You should not set WSGIPythonHome for a start. Even in situations where it is set, you don’t set it to the executable path. As per documentation you set it to what sys.prefix is for Python installation you want to use.

http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIPythonHome

As for checking whether mod_wsgi working, read:

http://code.google.com/p/modwsgi/wiki/CheckingYourInstallation

and setup a WSGI hello world program first, not a complex Django system.

See:

http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide

and watch:

http://code.google.com/p/modwsgi/wiki/WhereToGetHelp?tm=6#Conference_Presentations

Check more discussion of this question.

I want to use nodejs on a linode machine that has debian lenny installed.
I want to have the latest version of nodejs and npm as well.

apt-get does not seem to know nodejs or possibly I don’t know how to use it.

in here: http://nodejs.org/dist/v0.6.6/ i see many files but I don’t know which of them I should use for the install (nor how).

I am guessing that I need node-v0.6.6.pkg but again, this is just a guess and I don’t know how to continue from here.

thanks.

The .pkg file is for OSX. There are some repositories that have binaries for Debian, but it is probably easiest to download and compile the code. NodeJS is updated very frequently – so most repositories have very outdated versions. You will need some development tools (compiler, etc.) to be able to build the source.

sudo apt-get update
sudo apt-get install curl build-essential openssl libssl-dev

You can either download the source from the Node.JS site or pull it from github. The advantage of the latter is ease of maintenance.

NodeJS:

If you wish, you can install node to a directory other than the default, by adding –prefix /path/to/install/directory to your configure line, below. (Only use one of the following, not both)

From GitHub:

sudo apt-get install git-core
cd /usr/local/src ##or whatever directory you like#
git clone https://github.com/joyent/node.git && cd node
./configure
make
sudo make install

From source – tarball:

cd /usr/local/src ##or whatever directory you like#
wget http://nodejs.org/dist/v0.6.6/node-v0.6.6.tar.gz
tar -xzvf node-v0.6.6.tar.gz
cd node-v0.6.6
./configure
make
sudo make install

NPM:

NPM is already included with recent versions of node. Verify that it is installed with npm -v. If a version is displayed, there is no need to do the step below. If the ‘easy install’ doesn’t work for you, you can also download the code and make install.

curl http://npmjs.org/install.sh | sudo sh

Check more discussion of this question.

I wonder how can I install this in a lenny machine. Well, this site has instructions on how to do this, but in step 3 I can’t do cd /usr/local/meteor because this folder doesn’t exist! How I can connect meteor server with apache2 and php? **I don’t know what version of Perl I have installed but when I type perl into the bash, doesn’t output command doesn’t exist.. Any help, would be useful.

I want to add meteor as a tag to my question but, the system doesn’t allow me. An administrator can fix it

The installation instruction on the meteor site suggests using /usr/local/meteor as the installation directory, means you have to manually create it first (!).

mkdir /usr/local/meteor

After that you switch into it the newly created directory (cd /usr/local/meteor) AND AFTER that you continue the step by step instructions starting with wget ....

To “connect” apache2/php with meteor you have to run mod_proxy and reverse proxy meteor. Search for mod_proxy on how to do this. serverfault.com should provide you with the required information about mod_proxy.

Check more discussion of this question.

I’m setting up an environment to install many Lenny machines at once and I need to avoid any dialog with the process, corner cases aside. One thing that consistently troubles me is that after my preseeded disk recipe creates Linux RAID-1 devices, the installer warns me about how the kernel could not re-read the partition table on each MD device. When I do a manual installation and try to use debconf-get-selections to preseed another installation, it seems to ignore the whole preseed file altogether. But reading through those selections, I couldn’t find anything that seemed to suggest it would select “OK” on this extraneous warning.

For anybody else stuck on this issue, you can use the following line in your preseed file:

d-i partman/exception_handler_note note

But you’ll want to be aware of the implied risks.

Check more discussion of this question.

I need to monitor my postfix, dovecot and sasl process and start them if something go wrong.
I read about daemontools and I want it to monitor mail services.
Can I find somewhere step by step guide to setup daemontools on Debian? I’ve already installed
daemontools and daemontools-run packages.

daemontools is not really a meant to be used as a monitoring system for existing services. It is more of a framework for creating daemonized services that happens to have builtin self-monitoring and auto-restarting capabilities.

With a great deal of effort, you may be able to retrofit the postfix, dovecot, and sasl processes to run within the daemontools framework, but I can almost certainly guarantee that your time will be much better spent learning a tool better suited for what you want to accomplish.

I recommend you look into monit. It is packaged for Debian and should work well with the other Debian-packaged services that you want to monitor.

Check more discussion of this question.