Upgrade Trouble

You have a problem with Salix? Post here and we'll do what we can to help.
Post Reply
User avatar
Atip
Posts: 539
Joined: 5. Jun 2011, 04:27

Upgrade Trouble

Post by Atip »

I upgraded my 14.1 box to 14.2 following the instructions in how to upgrade.

Now on reboot it hangs when it comes to:

Code: Select all

Starting System message bus:.........
Unknown username "avahi" in message bus configuration file.
Unknown username "avahi" in message bus configuration file.
(yes twice)
Starting ConsoleKit daemon: /usr/bin/console-kit-daemon
Then booting stops.
KB is not disabled and I can reboot with Ctrl-Alt-Delete.

How do I correct this and get rid of the avahi, whatever that is.
I can access the partition with Slackel or Salix-14.2RC2
User avatar
gapan
Salix Wizard
Posts: 6361
Joined: 6. Jun 2009, 17:40

Re: Upgrade Trouble

Post by gapan »

I guess you can chroot into that partition and remove the avahi package. Something like this (with root priviliges):

Code: Select all

mkdir /mnt/salix
mount /dev/yourpartition /mnt/salix
chroot /mnt/salix
spkg -d avahi
I guess you could also create the respective user and group that avahi needs:

Code: Select all

groupadd -g 214 avahi
useradd -u 214 -g 214 -c 'Avahi' -d /dev/null -s /bin/false avahi
Image
Image
User avatar
Atip
Posts: 539
Joined: 5. Jun 2011, 04:27

Re: Upgrade Trouble

Post by Atip »

gapan wrote:I guess you can chroot into that partition and remove the avahi package. Something like this (with root priviliges):

Code: Select all

mkdir /mnt/salix
mount /dev/yourpartition /mnt/salix
chroot /mnt/salix
spkg -d avahi
[/code]
Thanks gapan. Great Linux OS and people behinid it. :)

Got rid of avahi, however, it turns out that this is apparently not the culprit.
First i found that the console-kit-daemon is not in /usr/bin/ as booting indicated
but in /usr/sbin/. I made a symlink. That did not change the fact that booting
stopped at that point.

Then pressing Ctrl-Alt-SysRq I will get 3 lines of messages. As longer i wait and
press again the higher the number in [ ] and in front of the boot messages becomes.

Here is the outout of those messages.

Code: Select all

 Aug 23 20:06:13 smartbro kernel: [   80.196623] input: SIGMACHIP Usb Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/0003:1C4F:0032.0004/input/input15
Aug 23 20:06:13 smartbro kernel: [   80.247178] hid-generic 0003:1C4F:0032.0004:
 input,hidraw0: USB HID v1.10 Mouse [SIGMACHIP Usb Mouse] on usb-0000:00:1d.1-2/input0
Aug 23 20:06:13 smartbro mtp-probe: checking bus 3, device 3:
"/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2"
Aug 23 20:06:13 smartbro mtp-probe: bus: 3, device: 3 was not an MTP device
Aug 23 20:06:46 smartbro kernel: [  113.577570] sysrq: SysRq : HELP :
loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f)- kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l)
- show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p)
- show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V)
- show-blocked-tasks(w) dump-ftrace-buffer(z)
Hope this will help you trying to solve this problem. It might not be Greek to you. ;)
For the record, KB is not locked and I can reboot with Ctrl-Alt-Delete.
User avatar
gapan
Salix Wizard
Posts: 6361
Joined: 6. Jun 2009, 17:40

Re: Upgrade Trouble

Post by gapan »

Atip wrote:Got rid of avahi, however, it turns out that this is apparently not the culprit.
First i found that the console-kit-daemon is not in /usr/bin/ as booting indicated
but in /usr/sbin/. I made a symlink. That did not change the fact that booting
stopped at that point.
Did you run dotnew after upgrading the packages and before rebooting? It seems that you are using an old rc.consolekit script.
Image
Image
User avatar
Atip
Posts: 539
Joined: 5. Jun 2011, 04:27

Re: Upgrade Trouble

Post by Atip »

gapan wrote:
Atip wrote:Got rid of avahi, however, it turns out that this is apparently not the culprit.
First i found that the console-kit-daemon is not in /usr/bin/ as booting indicated
but in /usr/sbin/. I made a symlink. That did not change the fact that booting
stopped at that point.
Did you run dotnew after upgrading the packages and before rebooting? It seems that you are using an old rc.consolekit script.
Your are a genious gapan! :P

Copied now rc.consolekit from Salix-14.2 to this box and booted into it. :D

I did run dotnew. There is no rc.consolekit.org or *.new in rc.d only the old rc.consolekit was there.

If I am reborn I will learn Greek for sure. ;)
Post Reply