A few things still aren’t working, so I’m popping up a post more as a reminder to myself on what’s left and how I fixed things more than anything.

SWAT

The Samba Web Administration Tool isn’t working for some reason. Whenever I attempt to connect to localhost:901 I get an error message that says:

The connection was refused when attempting to contact localhost:901

I’ve added the necessary lines to /etc/inetd.conf and /etc/services so I’m a bit confused on this one.

/etc/inetd.conf:

swat stream tcp nowait.400 root /usr/sbin/tcpd /usr/sbin/swat

/etc/services:

swat 901/tcp #swat

Cacti

The php script that cacti runs is throwing a bunch of errors each time it runs.

PHP Warning: Unknown(): Unable to load dynamic library ‘/usr/lib/php4/20050606/odbc.so’ – /usr/lib/php4/20050606/odbc.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: Unknown(): Unable to load dynamic library ‘/usr/lib/php4/20050606/pgsql.so’ – /usr/lib/php4/20050606/pgsql.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: Unknown(): Unable to load dynamic library ‘/usr/lib/php4/20050606/sybase_ct.so’ – /usr/lib/php4/20050606/sybase_ct.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: Unknown(): Unable to load dynamic library ‘/usr/lib/php4/20050606/odbc.so’ – /usr/lib/php4/20050606/odbc.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: Unknown(): Unable to load dynamic library ‘/usr/lib/php4/20050606/pgsql.so’ – /usr/lib/php4/20050606/pgsql.so: cannot open shared object file: No such file or directory in Unknown on line 0
PHP Warning: Unknown(): Unable to load dynamic library ‘/usr/lib/php4/20050606/sybase_ct.so’ – /usr/lib/php4/20050606/sybase_ct.so: cannot open shared object file: No such file or directory in Unknown on line 0

I’m feeling pretty retarded about this… I was missing a few php4 packages and snmpd wasn’t installed.

CUPS (printing)
Whenever I try to run /etc/init.d/cupsys start it fails and throws the following in syslog:

Feb 15 23:57:41 localhost hpiod: unable to ParDevice::Open hp:/par/ANY?device=/dev/parport0: No such file or directory: io/hpiod/ppdevice.cpp 827
Feb 15 23:57:41 localhost hpiod: unable to ParDevice::Open hp:/par/ANY?device=/dev/parport1: No such file or directory: io/hpiod/ppdevice.cpp 827
Feb 15 23:57:41 localhost hpiod: unable to ParDevice::Open hp:/par/ANY?device=/dev/parport2: No such file or directory: io/hpiod/ppdevice.cpp 827
Feb 15 23:57:41 localhost hpiod: unable to ParDevice::Open hp:/par/ANY?device=/dev/parport3: No such file or directory: io/hpiod/ppdevice.cpp 827

After reinstalling cupsys, these errors are still thrown to syslog each time but printing works.

DHCP
For some reason, I wasn’t getting a DHCP lease. The ethernet adapter wasn’t coming up on boot like it should. Whenever I ran dhclient, it would throw this output:

sit0: unknown hardware address type 776
execve (/lib/dhcp3-client/call-dhclient-script, …): Permission denied
execve (/lib/dhcp3-client/call-dhclient-script, …): Permission denied
execve (/lib/dhcp3-client/call-dhclient-script, …): Permission denied
execve (/lib/dhcp3-client/call-dhclient-script, …): Permission denied
sit0 -: unknown hardware address type 776
Listening on LPF/sit0/
Sending on LPF/sit0/
Listening on LPF/eth1/00:02:b3:19:58:4c
Sending on LPF/eth1/00:02:b3:19:58:4c
Listening on LPF/eth0/00:02:b3:19:50:3a
Sending on LPF/eth0/00:02:b3:19:50:3a
Listening on LPF/lo/
Sending on LPF/lo/
Sending on Socket/fallback
receive_packet failed on sit0: Network is down
receive_packet failed on eth1: Network is down
DHCPDISCOVER on sit0 to 255.255.255.255 port 67 interval 3
send_packet: Network is down
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
send_packet: Network is down
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on sit0 to 255.255.255.255 port 67 interval 4
send_packet: Network is down
DHCPACK from 10.0.0.2
execve (/lib/dhcp3-client/call-dhclient-script, …): Permission denied
bound to 10.0.0.50 — renewal in 38150 seconds.

There’s nothing wrong with that, except that it wouldn’t actually bind the IP address to eth0. After manually configuring the interface and setting up a route to our gateway, I had internet access. An apt-get install --reinstall dhcp3-client later, it was fixed. I’m still not sure what exactly was wrong.

Postfix
Postfix wasn’t delivering mail non-locally. It was dumping error messages in syslog that said:

Once I checked out /var/spool/postfix I was able to determine that the permissions were all wrong. Once again, apt-get install --reinstall postfix fixed the problem.

Samba

For some reason, when I attempt to connect to any shares that I have defined, it rejects my username and password. The permissions all appear correct in /etc/samba/, so I’m not sure what’s going on.

Apparently, /etc/samba/smbpasswd is not the file that Samba actually pulls passwords from. Recreating the users enabled connecting to the shares again.

WebDAV

It seems to authenticate, however throws the following errors to /var/log/apache2/errors.log:

[Wed Feb 15 21:58:36 2006] [error] [client 10.0.10.27] Could not DELETE /calendars/Personal.ics due to a failed precondition (e.g. locks). [500, #0]
[Wed Feb 15 21:58:36 2006] [error] [client 10.0.10.27] The locks could not be queried for verification against a possible “If:” header. [500, #0]
[Wed Feb 15 21:58:36 2006] [error] [client 10.0.10.27] Could not open the lock database. [500, #400]
[Wed Feb 15 21:58:36 2006] [error] [client 10.0.10.27] (2)No such file or directory: Could not open property database. [500, #1]
[Wed Feb 15 21:58:36 2006] [error] [client 10.0.10.27] The locks could not be queried for verification against a possible “If:” header. [500, #0]
[Wed Feb 15 21:58:36 2006] [error] [client 10.0.10.27] Could not open the lock database. [500, #400]
[Wed Feb 15 21:58:36 2006] [error] [client 10.0.10.27] (2)No such file or directory: Could not open property database. [500, #1]

WebDAV was restored to a normal state by creating the lock database /var/lock/DAV/DAVLock (chowned to www-data) as defined in /etc/apache2/apache2.conf

#LoadModule dav_fs_module modules/mod_dav_fs.so
DAVLockDB /var/lock/DAV/DAVLock