Not able to start services through GUI

[juicer]

Hi,

for some time I have not been able to start services through the web GUI. For example, when checking the "Printing" box, updating, and then switching to the "Printing" page it is not possible to add a printer and a message says that the service is disabled. The same is true for up and downloads.

I have been waiting for the etch update with the intention to reinstall everything. But now I do not want to wait anymore. Can anyone help me out with this problem?

Regards,
Björn

[Cheeseboy]

Hello juicer,

Have you got any idea of what was changed since it did work?
Have you checked the logfiles for clues?

Regards,

Cheeseboy

[juicer]

No, regrettably I don't have a clue. I had some trouble during one upgrade which resulted in that my swap partition got lost(!) I got good help here at the forum, though, and was able to fix that. I think that was when this error started but I didn't care at the time because I wanted to re-install and upgrade to etch anyway (now that option seems to be a dist upgrade instead).

So, if anyone knows where to start looking it would be much appreciated!

Thanks,
Björn

[tor]

Hi Juicer,

Could you try to enable the service on the command line? As root do

Code: Select all

/etc/init.d/cupsys start

And see what that says. (Should start the printing service)

/Tor

[juicer]

Hi Tor,

there are no error messages if I try to start the service manually:

Code: Select all

bubba:~# /etc/init.d/cupsys start
Starting Common Unix Printing System: cupsdbubba:~#

However, the service is still marked as disabled in the GUI (as all other services). But when doing a ps the daemon seems to be up and running.

Code: Select all

bubba:~# ps aux | grep cups
root      6462  0.0  2.5  7348 1608 ?        Ss   06:31   0:00 /usr/sbin/cupsd -F
root     15152  0.0  0.9  3544  592 pts/0    S+   15:49   0:00 grep cups
bubba:~#

/Björn

[juicer]

Any ideas, someone?

/Björn

[6feet5]

Hi,

Maybe the output of the following commands can give some clue as to what is the problem (assuming FTP also has this problem). First log on as root then run:

Code: Select all

/usr/lib/web-admin/backend.pl add_service proftpd
/usr/lib/web-admin/backend.pl start_service proftpd

Also, show us the content of /etc/rc2.d after you have started the FTP service :

Code: Select all

ls -l /etc/rc2.d

.

/Johan

[juicer]

Hi Johan,

thank you for your answer. I did the following:

Code: Select all

bjorn@bubba:~$ su -
Password:
bubba:~# /usr/lib/web-admin/backend.pl add_service proftpd
proftpd already in /etc/runlevel.conf: No change.
bubba:~# ftp localhost
Connected to localhost.
220 ProFTPD 1.2.10 Server (Bubba) [127.0.0.1]
Name (localhost:bjorn):
331 Password required for bjorn.
Password:
230 User bjorn logged in.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> by
221 Goodbye.
bubba:~# /usr/lib/web-admin/backend.pl start_service proftpd
Starting ProFTPD ftp daemon: .
bubba:~# ps -ef | grep ft
root         2     1  0 Apr29 ?        00:00:00 [ksoftirqd/0]
root      1107     1  0 Apr29 ?        00:00:00 /usr/sbin/ftd.bin
root      1113  1107  0 Apr29 ?        00:00:01 /usr/sbin/ftd.bin
root      1114  1113  0 Apr29 ?        00:01:39 /usr/sbin/ftd.bin
root      1117  1113  0 Apr29 ?        00:00:00 /usr/sbin/ftd.bin
root      1120  1113  0 Apr29 ?        00:00:05 /usr/sbin/ftd.bin
root      1122  1113  0 Apr29 ?        00:00:00 /usr/sbin/ftd.bin
nobody    1361     1  0 Apr29 ?        00:00:00 proftpd: (accepting connections)
root       836   819  3 12:51 pts/0    00:00:00 grep ft
bubba:~# ls -l /etc/rc2.d
total 0
lrwxrwxrwx 1 root root 16 2008-04-08 21:16 S99led_on -> ../init.d/led_on
bubba:~#

When I saw that /etc/rc2.d was almost empty except for 'S99led_on', I had a look at my colleague's /etc/rc* directories and he had a lot more stuff there. Mine are all empty except for the led stuff. /etc/init.d looks ok, though

Code: Select all

bubba:~# ls -la /etc/rc*
/etc/rc0.d:
total 8
drwxr-xr-x  2 root root 4096 2008-04-08 21:16 .
drwxr-xr-x 63 root root 4096 2008-04-29 13:02 ..
lrwxrwxrwx  1 root root   19 2008-04-08 21:16 K10led_blink -> ../init.d/led_blink
lrwxrwxrwx  1 root root   17 2008-04-08 21:16 S89led_off -> ../init.d/led_off

/etc/rc2.d:
total 8
drwxr-xr-x  2 root root 4096 2008-04-08 21:16 .
drwxr-xr-x 63 root root 4096 2008-04-29 13:02 ..
lrwxrwxrwx  1 root root   16 2008-04-08 21:16 S99led_on -> ../init.d/led_on

/etc/rc6.d:
total 8
drwxr-xr-x  2 root root 4096 2008-04-08 21:16 .
drwxr-xr-x 63 root root 4096 2008-04-29 13:02 ..
lrwxrwxrwx  1 root root   19 2008-04-08 21:16 K10led_blink -> ../init.d/led_blink

/etc/rcS.d:
total 8
drwxr-xr-x  2 root root 4096 2008-04-08 21:16 .
drwxr-xr-x 63 root root 4096 2008-04-29 13:02 ..
lrwxrwxrwx  1 root root   19 2008-04-08 21:16 S53bubba-cfg -> ../init.d/bubba-cfg

bubba:~# ls -l /etc/init.d
total 328
-rwxr-xr-x 1 root root 3583 2006-09-27 22:22 apache2
-rwxr-xr-x 1 root root 1074 2006-09-27 22:22 atd
-rwxr-xr-x 1 root root 4038 2007-05-29 23:07 avahi-daemon
-rwxr-xr-x 1 root root 4127 2007-05-29 23:07 avahi-dnsconfd
-rw-r--r-- 1 root root 2593 2005-01-05 01:28 bootclean.sh
-rwxr-xr-x 1 root root 1529 2006-09-27 22:22 bootlogd
-rwxr-xr-x 1 root root 1371 2006-09-27 22:22 bootmisc.sh
-rwxrwxrwx 1 root root  410 2007-09-05 16:07 bubba-cfg
-rwxr-xr-x 1 root root  935 2006-09-27 22:22 checkfs.sh
-rwxr-xr-x 1 root root 7160 2006-09-27 22:22 checkroot.sh
-rwxr-xr-x 1 root root 5366 2006-09-27 22:22 console-screen.sh
-rwxr-xr-x 1 root root 1096 2006-09-27 22:22 cron
-rwxr-xr-x 1 root root 1647 2006-09-27 22:22 cupsys
-rwxrwxrwx 1 root root 2103 2007-08-23 10:53 dbus-daemon
-rwxr-xr-x 1 root root  729 2006-09-27 22:22 dns-clean
-rwxr-xr-x 1 root root 2251 2006-09-27 22:22 dovecot
-rwxr-xr-x 1 root root 5592 2006-09-27 22:22 fetchmail
-rwxrwxrwx 1 root root 1788 2008-04-07 17:36 ftd
-rwxr-xr-x 1 root root 5821 2007-02-22 06:01 glibc.sh
-rwxr-xr-x 1 root root  811 2006-09-27 22:22 halt
-rwxr-xr-x 1 root root 6736 2006-09-27 22:22 hdparm
-rwxr-xr-x 1 root root  165 2006-09-27 22:22 hostname.sh
-rwxr-xr-x 1 root root 3344 2006-09-27 22:22 hotplug
-rwxr-xr-x 1 root root  359 2006-09-27 22:22 hotplug-net
-rwxr-xr-x 1 root root 3499 2006-09-27 22:22 hwclockfirst.sh
-rwxr-xr-x 1 root root 3638 2006-09-27 22:22 hwclock.sh
-rwxr-xr-x 1 root root 3415 2006-09-27 22:22 ifplugd
-rwxr-xr-x 1 root root 2518 2006-09-15 20:03 ifupdown
-rwxr-xr-x 1 root root 1046 2006-09-15 20:03 ifupdown-clean
-rwxr-xr-x 1 root root 2923 2006-09-27 22:22 keymap.sh
-rwxr-xr-x 1 root root 1346 2006-09-27 22:22 klogd
-rwxrwxrwx 1 root root   48 2007-09-05 16:07 led_blink
-rwxrwxrwx 1 root root   34 2007-09-05 16:07 led_off
-rwxrwxrwx 1 root root   33 2007-09-05 16:07 led_on
-rwxr-xr-x 1 root root  798 2006-09-27 22:22 makedev
-rwxr-xr-x 1 root root 2179 2007-03-28 18:06 mediatomb
-rwxr-xr-x 1 root root 1320 2006-09-27 22:22 module-init-tools
-rwxr-xr-x 1 root root  864 2006-09-27 22:22 modutils
-rwxr-xr-x 1 root root 1033 2006-09-27 22:22 mountall.sh
-rwxr-xr-x 1 root root 1619 2006-09-27 22:22 mountnfs.sh
-rwxr-xr-x 1 root root 4872 2006-09-27 22:22 mountvirtfs
-rwxr-xr-x 1 root root 1725 2007-08-02 13:08 mt-daapd
-rwxr-xr-x 1 root root 4220 2006-08-29 14:40 mysql
-rwxr-xr-x 1 root root 2550 2007-01-06 16:36 networking
-rwxr-xr-x 1 root root  659 2005-08-27 11:37 ntpdate
-rwxr-xr-x 1 root root 2305 2006-09-27 22:22 nviboot
-rwxr-xr-x 1 root root 2324 2007-03-21 19:25 openbsd-inetd
-rwxr-xr-x 1 root root 1076 2005-03-20 11:01 portmap
-rwxr-xr-x 1 root root 2974 2007-03-13 06:51 postfix
-rwxr-xr-x 1 root root 1452 2006-09-27 22:22 ppp
-rwxr-xr-x 1 root root  189 2006-09-27 22:22 pppd-dns
-rwxr-xr-x 1 root root 1039 2006-09-27 22:22 procps.sh
-rwxr-xr-x 1 root root 3762 2006-09-27 22:22 proftpd
-rwxr-xr-x 1 root root 6534 2004-08-14 18:47 rc
-rwxr-xr-x 1 root root 3191 2004-08-14 18:47 rcS
-rw-r--r-- 1 root root  939 2004-08-14 18:47 README
-rwxr-xr-x 1 root root  197 2006-09-27 22:22 reboot
-rwxr-xr-x 1 root root  457 2006-09-27 22:22 rmnologin
-rwxr-xr-x 1 root root 1763 2006-09-27 22:22 samba
-rwxr-xr-x 1 root root  358 2006-09-27 22:22 sendsigs
-rwxr-xr-x 1 root root  591 2006-09-27 22:22 single
-rwxr-xr-x 1 root root 2111 2005-01-05 01:28 skeleton
-rwxr-xr-x 1 root root 2826 2006-12-15 01:23 slimserver
-rwxr-xr-x 1 root root 1891 2006-09-27 22:22 ssh
lrwxrwxrwx 1 root root    8 2008-01-03 00:14 stop-bootlogd -> bootlogd
-rwxr-xr-x 1 root root  354 2006-09-27 22:22 sudo
-rwxr-xr-x 1 root root 2077 2006-09-27 22:22 sysklogd
-rwxr-xr-x 1 root root 6138 2006-09-27 22:22 udev
-rwxr-xr-x 1 root root  854 2006-09-27 22:22 udev-mtab
-rwxr-xr-x 1 root root  509 2006-09-27 22:22 umountfs
-rwxr-xr-x 1 root root 1291 2006-09-27 22:22 umountnfs.sh
-rwxr-xr-x 1 root root 1381 2006-09-27 22:22 urandom
-rwxr-xr-x 1 root root 1963 2007-01-07 14:17 xfree86-common

I am no expert on how Linux starts but I am surprised that my bubba is working at all... Can I just recreate the links in the directories or what do I do?

Regards,
Björn

[6feet5]

Hi,

That message about /etc/runlevel.conf is a bit confusing to me. I have no such file and from what I can tell it belongs to a package called file-rc which in turn appears to be an alternative to the usual SysV init scheme which use the /etc/rc?.d. I'm guessing something is corrupt with your install. What version of the firmware are you running?

/Johan

[juicer]

I am running the latest version, 0.52.2-1

/Björn

[6feet5]

I realized I wasn't running the latest version so I have upgraded but no such file (/etc/runlevel.conf).

Run the following command as root:

Code: Select all

dpkg --get-selections|grep 'file-rc'

If you get a line saying it is installed, then that is probably the reason to your problem because that package will not use the /etc/rc?.d folder (which the web-admin pages depend on).

Have you installed anything that depend on the 'file-rc' package?

Are you a dare-devil? No guts, no glory You could try and install the sysv-rc package (if file-rc was installed), and see what happen.

Code: Select all

apt-get install sysv-rc

/Johan

[juicer]

Yes, you are correct! I have the file-rc package installed. I have no clue on why it is installed, though...

When reading the package description it says that it will convert back from /etc/runlevel.conf to the old symlinks in the /etc/rc?.d if removed. Wouldn't that be an option? Or would I crash something else then?

Regards,
Björn

[6feet5]

My guess is it is safe to restore the old sysv-rc package. It's hard to tell for sure though when I don't know what caused the package to be installed in the first place.

You can run aptitude to see what packages depend on 'file-rc'. If you don't have aptitude installed, you could try the following:

Code: Select all

dpkg --get-selections|awk '{print $1}'|xargs dpkg -p|awk '/Package:/{pkgname=$2} /file-rc/{ print pkgname }'

It will examine all installed packages and print the name of any package that mention the 'file-rc' package. You can then examine this package closer with

Code: Select all

dpkg -p

Work your way up the dependency tree until you get to the cause.

Or you could just try:

Code: Select all

apt-get install sysv-rc

Your call

/Johan