« previous next »
Pages: [1] 2 3 4   Go Down

Author Topic: System won't boot after update. SOLVED  (Read 3062 times)

Offline Snapshot

  • Hero Member
  • *****
  • Posts: 610
System won't boot after update. SOLVED
« on: June 15, 2011, 09:26:00 AM »
While there is another similar thread already posted it doesn't seem to be the sole topic of my problem.  Two days ago when I updated via Synaptic I rebooted and my system will not boot up.  I am dropped into a limited shell and cannot log in even as root.  Typing "startx" gives me a not recognized command error.  Prior to that particular error is a screen full of other messages and text which doesn't mean anything to me.  I posted on the other thread but no suggestions were made nor was there any information given on what might have happened or how to fix my problem.  That being the case I hope by starting a new thread I might be able to fix the problem without reinstalling.  I am completely at a loss why this happened and what to do about it.  Help.

Thanks.
« Last Edit: June 22, 2011, 08:17:15 AM by Snapshot »
Logged
If fishing is interfering
with your business, give
up your business.
Sparse Grey Hackle
(Alfred W. Miller)

Offline rubentje1991

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 2110
  • Rubenus Parvus MCMXCI
Re: System won't boot after update.
« Reply #1 on: June 15, 2011, 09:32:15 AM »
May we see that "not recognized command error"?

If you search in the Xorg-migration section, you'll find following commands:

(as superuser:)
Code: [Select]
rm -f /etc/X11/xorg.conf
XFdrake --auto
reboot:: did you try them?


PS: please can you post the URL of the other thread (then everyone knows what's already suggested - and what you already tried....)
Logged

Offline Snapshot

  • Hero Member
  • *****
  • Posts: 610
Re: System won't boot after update.
« Reply #2 on: June 15, 2011, 11:27:36 AM »
Quote from: rubentje1991 on June 15, 2011, 09:32:15 AM
May we see that "not recognized command error"?

If you search in the Xorg-migration section, you'll find following commands:

(as superuser:)
Code: [Select]
rm -f /etc/X11/xorg.conf
XFdrake --auto
reboot:: did you try them?


PS: please can you post the URL of the other thread (then everyone knows what's already suggested - and what you already tried....)
No I didn't try them as I can't log in and I wasn't familiar with the Xorg-migration section.  I'll try redo-mbr and see if that helps at all.  The link I referred to is this http://www.pclinuxos.com/forum/index.php?topic=92711.new;topicseen#new
Logged
If fishing is interfering
with your business, give
up your business.
Sparse Grey Hackle
(Alfred W. Miller)

Offline Snapshot

  • Hero Member
  • *****
  • Posts: 610
Re: System won't boot after update.
« Reply #3 on: June 15, 2011, 12:00:27 PM »
I'm not sure if I made myself clear on the bootup.  Everything looks "normal" up to the point where I select the login.  Once I've selected an account and the boot process starts is where the trouble begins.  I get many failed errors during the boot process; obviously as I have no way to capture them I can't post them.  On the other thread Texstar instructed someone to press f3 and then 3.  I tried safe mode and it made no difference.  Doing that only gives me kernel options and nothing else.  I'm running 4GB ram, nVidia 9400 video card and a AMD 64bit dual core cpu with 2 500GB sata WD hard drives if this helps at all.  I would really like (prefer) to fix the problem rather than reinstall if at all possible.  All I did was update my system through synaptic on June 13 and when I rebooted my system it failed.  redo-mbr isn't a recognized command either.
« Last Edit: June 15, 2011, 12:02:12 PM by Snapshot »
Logged
If fishing is interfering
with your business, give
up your business.
Sparse Grey Hackle
(Alfred W. Miller)

Offline Snapshot

  • Hero Member
  • *****
  • Posts: 610
Re: System won't boot after update.
« Reply #4 on: June 15, 2011, 12:31:51 PM »
Quote from: rubentje1991 on June 15, 2011, 09:32:15 AM
May we see that "not recognized command error"?

If you search in the Xorg-migration section, you'll find following commands:

(as superuser:)
Code: [Select]
rm -f /etc/X11/xorg.conf
XFdrake --auto
reboot:: did you try them?


PS: please can you post the URL of the other thread (then everyone knows what's already suggested - and what you already tried....)
I went back and tried what you suggested and NONE of the commands are found.

Thanks.
Logged
If fishing is interfering
with your business, give
up your business.
Sparse Grey Hackle
(Alfred W. Miller)

Offline Snapshot

  • Hero Member
  • *****
  • Posts: 610
Re: System won't boot after update.
« Reply #5 on: June 15, 2011, 04:29:21 PM »
Quote from: wedgetail on June 15, 2011, 04:11:21 PM
Snapshot
I am not getting involved, but have you tried to start up a liveCD (any) to make sure that does not fail. then explore the contents of your installed directories?  This might indicate a filesystem check needed (but I don't think so)   ;D 

Don't panick, unless necessary.   :D
Thanks for the reply.  I'm using a live cd (dvd backup) right now.  No, I haven't explored my directories as I don't know what I'm even looking for and if I found it I wouldn't know either.  I'm not panicking yet but I am extremely frustrated that I didn't do anything to cause this and feel like it shouldn't have happened in the first place.  I can't understand why I seem to be the only one experiencing this problem and why there doesn't seem to be a fix for it.  I've been a very happy PCLOS user since 2007 but right now I'm not a happy user at all.  More like a very UNhappy PCLOS user.  Even though I can install from my live dvd backup I shouldn't have to.  Not panicking but very close to it. >:(
Logged
If fishing is interfering
with your business, give
up your business.
Sparse Grey Hackle
(Alfred W. Miller)

Offline russ553

  • Jr. Member
  • **
  • Posts: 16
Re: System won't boot after update.
« Reply #6 on: June 15, 2011, 08:28:09 PM »
+1

I completely lost my computer today after that update and feel the same way you do.  You are not alone.
Logged
Been there, done that, don't remember.

Offline Snapshot

  • Hero Member
  • *****
  • Posts: 610
Re: System won't boot after update.
« Reply #7 on: June 15, 2011, 08:40:20 PM »
Quote from: russ553 on June 15, 2011, 08:28:09 PM
+1

I completely lost my computer today after that update and feel the same way you do.  You are not alone.
Russ, I'm so sorry to hear of your trouble that is more serious than mine.  I can reinstall if needed but like I stated before, I shouldn't have to because I didn't cause this problem.  Synaptic did and that isn't supposed to happen.  Period!  I'm losing confidence in PCLOS due to the lack of response to this problem.  This is serious and needs fixing asap.  I hope you have your files backed up somewhere safe.  Good luck to us both.
Logged
If fishing is interfering
with your business, give
up your business.
Sparse Grey Hackle
(Alfred W. Miller)

Offline muungwana

  • Hero Member
  • *****
  • Posts: 6201
Re: System won't boot after update.
« Reply #8 on: June 15, 2011, 08:41:40 PM »
You type in commands and none are found, you may have a file system corruption problem.

When you are at the log in screen,  press ctrl+alt+f1 to switch to that tty and then enter root for username and root's password to log in.

Once you are in, run this command and then reboot, it will force a file system check on system reboot.

/bin/touch /forcefsck

One system reboot, press "esc" key to remove that image thing to see the terminal to see if fsck will say anything about the file system.

When the system boots up again, do the above but then run these commands now

apt-get update
apt-get -dist-upgrade

when you are done enter "startx" and see if the desktop will come up or not
Logged
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline djohnston

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6227
  • I don't do Windows
Re: System won't boot after update.
« Reply #9 on: June 15, 2011, 10:31:40 PM »
Quote from: Snapshot on June 15, 2011, 12:00:27 PM
I'm not sure if I made myself clear on the bootup.  Everything looks "normal" up to the point where I select the login.  Once I've selected an account and the boot process starts is where the trouble begins.

If you're getting that far, then bootup is correct. It is starting the X server that isn't working.

Quote from: Snapshot on June 15, 2011, 12:00:27 PM
I get many failed errors during the boot process; obviously as I have no way to capture them I can't post them.  On the other thread Texstar instructed someone to press f3 and then 3.

Not exactly what he said, I'm pretty sure. Let's go through the procedure, step by step. Here's how I do it.

At the GRUB boot menu (the first menu you see), press the [Escape] key. A dialog box will come up and say your are leaving graphical mode. Answer OK. You will then see the same boot menu again, although the graphics will look different.

1. Press e. You will then see two lines of text.
2. Press e again. Your cursor will then be at the end of the first line. Press the space bar once, then enter the number 3.
3. Press [Return].
4. Press b to boot.

You will boot up into runlevel 3, without a GUI. At the login prompt, login as root. Then enter:

rm -f /etc/X11/xorg.conf
XFdrake --auto
reboot
« Last Edit: June 15, 2011, 10:34:35 PM by djohnston »
Logged
Bare metal                           VBox
AMD Athlon 7750 Dual-Core    Single core
4GiB RAM                              1GiB RAM
nVidia GeForce FX 5200          64MB video
LXDE 32bit                            KDE 64bit

Registered Linux User #416378

Offline Snapshot

  • Hero Member
  • *****
  • Posts: 610
Re: System won't boot after update.
« Reply #10 on: June 15, 2011, 11:00:27 PM »
Quote from: djohnston on June 15, 2011, 10:31:40 PM
Quote from: Snapshot on June 15, 2011, 12:00:27 PM
I'm not sure if I made myself clear on the bootup.  Everything looks "normal" up to the point where I select the login.  Once I've selected an account and the boot process starts is where the trouble begins.

If you're getting that far, then bootup is correct. It is starting the X server that isn't working.

Quote from: Snapshot on June 15, 2011, 12:00:27 PM
I get many failed errors during the boot process; obviously as I have no way to capture them I can't post them.  On the other thread Texstar instructed someone to press f3 and then 3.

Not exactly what he said, I'm pretty sure. Let's go through the procedure, step by step. Here's how I do it.

At the GRUB boot menu (the first menu you see), press the [Escape] key. A dialog box will come up and say your are leaving graphical mode. Answer OK. You will then see the same boot menu again, although the graphics will look different.

1. Press e. You will then see two lines of text.
2. Press e again. Your cursor will then be at the end of the first line. Press the space bar once, then enter the number 3.
3. Press [Return].
4. Press b to boot.

You will boot up into runlevel 3, without a GUI. At the login prompt, login as root. Then enter:

rm -f /etc/X11/xorg.conf
XFdrake --auto
reboot

I regret that you are about 15 minutes too late as I've already started reinstalling from my backup live dvd.  If something like this happens again I will fall back on this post for help.  Thank you for your kind offer of help, I truly appreciate it.

Bob
Logged
If fishing is interfering
with your business, give
up your business.
Sparse Grey Hackle
(Alfred W. Miller)

Offline djohnston

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 6227
  • I don't do Windows
Re: System won't boot after update.
« Reply #11 on: June 15, 2011, 11:27:20 PM »
You're welcome, Bob. Even the best get into a pickle from time to time. It can happen even under the best of circumstances. I lost some data on an external USB recently due to a power surge. And everything's on UPS.

Logged
Bare metal                           VBox
AMD Athlon 7750 Dual-Core    Single core
4GiB RAM                              1GiB RAM
nVidia GeForce FX 5200          64MB video
LXDE 32bit                            KDE 64bit

Registered Linux User #416378

Offline muungwana

  • Hero Member
  • *****
  • Posts: 6201
Re: System won't boot after update.
« Reply #12 on: June 16, 2011, 01:36:12 PM »

what do these errors say? are they reading errors or some expected things are missing?

open "/var/log/syslog" text file with a text editor running with root's privileges and check to see if anything is reported there.

what desktop environment are you using, your system is set to use what locale?
Logged
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline Snapshot

  • Hero Member
  • *****
  • Posts: 610
Re: System won't boot after update.
« Reply #13 on: June 16, 2011, 02:11:08 PM »
Quote from: muungwana on June 16, 2011, 01:36:12 PM

what do these errors say? are they reading errors or some expected things are missing?

open "/var/log/syslog" text file with a text editor running with root's privileges and check to see if anything is reported there.

what desktop environment are you using, your system is set to use what locale?
-bash: WARNING: setlocale: LC_C Type: cannot change locale (eng_USUTF8): no such file or directory
-bash: WARNING: setlocale: LC_COLLATE: cannot change locale (eng_USUTF8): no such file or directory
-bash: WARNING: setlocale: NUMBER: cannot change locale (eng_USUTF8): no such file or directory
-bash: WARNING: setlocale: TIME: cannot change locale (eng_USUTF8): no such file or directory
-bash: WARNING: setlocale: MESSAGES: cannot change locale (eng_USUTF8): no such file or directory
/bin/unicode_start: line4: /usr/bin/tty: no such file or directory
unicode_start skipped on
-bash: dircolors: command not found
-bash: tty: command not found
-bash: gpg-agent: command not found
-bash: msg: command not found
 
 Jun 16 15:19:03 localhost syslogd 1.5.0: restart.
Jun 16 15:19:03 localhost dansguardian[6782]: Started sucessfully.
Jun 16 15:20:56 localhost klogd: ip_tables: (C) 2000-2006 Netfilter Core Team
Jun 16 15:20:57 localhost msec: Security Warning: these files shouldn't be owned by someone else or readable :
Jun 16 15:20:57 localhost msec: - /home/snapshot/.Xauthority : file is group readable.
Jun 16 15:20:57 localhost msec: - /home/snapshot/.Xauthority : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/snapshot/.gnupg/secring.gpg : file is group readable.
Jun 16 15:20:57 localhost msec: - /home/snapshot/.gnupg/secring.gpg : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.Xauthority : file is group readable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.Xauthority : file is other readable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.Xauthority : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.Xauthority : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.gnupg/secring.gpg : file is group readable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.gnupg/secring.gpg : file is other readable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.gnupg/secring.gpg : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.gnupg/secring.gpg : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.Xauthority : file is group readable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.Xauthority : file is other readable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.Xauthority : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.Xauthority : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.gnupg/secring.gpg : file is group readable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.gnupg/secring.gpg : file is other readable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.gnupg/secring.gpg : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.gnupg/secring.gpg : file is other writable.
Jun 16 15:20:57 localhost msec: Security Warning: theses files should not be owned by someone else or writable :
Jun 16 15:20:57 localhost msec: - /home/snapshot/.bashrc : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/snapshot/.bash_profile : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/snapshot/.bash_logout : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/snapshot/.gnupg : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/snapshot/.gnupg/secring.gpg : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/snapshot/.Xauthority : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/snapshot/.config : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.bashrc : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.bashrc : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.bash_profile : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.bash_profile : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.bash_logout : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.bash_logout : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.gnupg : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.gnupg : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.gnupg/secring.gpg : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.gnupg/secring.gpg : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.Xauthority : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.Xauthority : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.config : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/kansas/.config : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.bashrc : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.bashrc : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.bash_profile : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.bash_profile : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.bash_logout : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.bash_logout : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.gnupg : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.gnupg : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.gnupg/secring.gpg : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.gnupg/secring.gpg : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.Xauthority : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.Xauthority : file is other writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.config : file is group writable.
Jun 16 15:20:57 localhost msec: - /home/shutterbug/.config : file is other writable.
Jun 16 15:20:57 localhost msec: Security Warning: these home directory should not be owned by someone else or writable :
Jun 16 15:20:57 localhost msec: user=uuidd(493) : home directory is group writable.
Jun 16 15:20:57 localhost msec: user=snapshot(500) : home directory is group writable.
Jun 16 15:20:57 localhost msec: user=kansas(501) : home directory is group writable.
Jun 16 15:20:57 localhost msec: user=kansas(501) : home directory is other writable.
Jun 16 15:20:57 localhost msec: user=shutterbug(503) : home directory is group writable.
Jun 16 15:20:57 localhost msec: user=shutterbug(503) : home directory is other writable.
Jun 16 15:20:57 localhost msec: These are the ports listening on your machine :
Jun 16 15:20:57 localhost msec: Active Internet connections (only servers)
Jun 16 15:20:57 localhost msec: Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
Jun 16 15:20:57 localhost msec: tcp        0      0 *:ipp                       *:*                         LISTEN      2348/cupsd
Jun 16 15:20:57 localhost msec: tcp        0      0 localhost.localdomain:smtp  *:*                         LISTEN      3084/master
Jun 16 15:20:57 localhost msec: tcp        0      0 *:30020                     *:*                         LISTEN      2810/python
Jun 16 15:20:57 localhost msec: tcp        0      0 *:sane-port                 *:*                         LISTEN      2536/xinetd
Jun 16 15:20:57 localhost msec: tcp        0      0 localhost.localdomain:10026 *:*                         LISTEN      3084/master
Jun 16 15:20:57 localhost msec: tcp        0      0 *:webcache                  *:*                         LISTEN      6782/dansguardian
Jun 16 15:20:57 localhost msec: tcp        0      0 *:ssh                       *:*                         LISTEN      2364/sshd
Jun 16 15:20:57 localhost msec: tcp        0      0 *:ipp                       *:*                         LISTEN      2348/cupsd
Jun 16 15:20:57 localhost msec: tcp        0      0 *:ssh                       *:*                         LISTEN      2364/sshd
Jun 16 15:20:57 localhost msec: udp        0      0 *:5353                      *:*                                     2544/avahi-daemon:
Jun 16 15:20:57 localhost msec: udp        0      0 *:1900                      *:*                                     2810/python
Jun 16 15:20:57 localhost msec: udp        0      0 *:45945                     *:*                                     2544/avahi-daemon:
Jun 16 15:20:57 localhost msec: udp        0      0 *:33286                     *:*                                     2810/python
Jun 16 15:20:57 localhost msec: udp        0      0 *:bootpc                    *:*                                     2184/dhclient
Jun 16 15:20:57 localhost msec: udp        0      0 *:58448                     *:*                                     2184/dhclient
Jun 16 15:20:57 localhost msec: udp        0      0 *:ipp                       *:*                                     2348/cupsd
Jun 16 15:20:57 localhost msec: udp        0      0 linux.local:ntp             *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: udp        0      0 localhost.localdomain:ntp   *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: udp        0      0 *:ntp                       *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: udp        0      0 *:53106                     *:*                                     2184/dhclient
Jun 16 15:20:57 localhost msec: udp        0      0 ::1:ntp                     *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: udp        0      0 fe80::230:67ff:fe01:ntp     *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: udp        0      0 *:ntp                       *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: Security Warning: change in network listening ports found :
Jun 16 15:20:57 localhost msec: -   Added network listening ports : tcp        0      0 *:ipp                       *:*                         LISTEN      2348/cupsd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : tcp        0      0 localhost.localdomain:smtp  *:*                         LISTEN      3084/master
Jun 16 15:20:57 localhost msec: -   Added network listening ports : tcp        0      0 *:30020                     *:*                         LISTEN      2810/python
Jun 16 15:20:57 localhost msec: -   Added network listening ports : tcp        0      0 *:sane-port                 *:*                         LISTEN      2536/xinetd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : tcp        0      0 localhost.localdomain:10026 *:*                         LISTEN      3084/master
Jun 16 15:20:57 localhost msec: -   Added network listening ports : tcp        0      0 *:webcache                  *:*                         LISTEN      6782/dansguardian
Jun 16 15:20:57 localhost msec: -   Added network listening ports : tcp        0      0 *:ssh                       *:*                         LISTEN      2364/sshd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : tcp        0      0 *:ipp                       *:*                         LISTEN      2348/cupsd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : tcp        0      0 *:ssh                       *:*                         LISTEN      2364/sshd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 *:5353                      *:*                                     2544/avahi-daemon:
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 *:1900                      *:*                                     2810/python
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 *:45945                     *:*                                     2544/avahi-daemon:
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 *:33286                     *:*                                     2810/python
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 *:bootpc                    *:*                                     2184/dhclient
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 *:58448                     *:*                                     2184/dhclient
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 *:ipp                       *:*                                     2348/cupsd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 linux.local:ntp             *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 localhost.localdomain:ntp   *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 *:ntp                       *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 *:53106                     *:*                                     2184/dhclient
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 ::1:ntp                     *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 fe80::230:67ff:fe01:ntp     *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: -   Added network listening ports : udp        0      0 *:ntp                       *:*                                     2403/ntpd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : tcp        0      0 *:ipp                       *:*                         LISTEN      2427/cupsd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : tcp        0      0 localhost.localdomain:smtp  *:*                         LISTEN      2987/master
Jun 16 15:20:57 localhost msec: - Removed network listening ports : tcp        0      0 *:30020                     *:*                         LISTEN      2830/python
Jun 16 15:20:57 localhost msec: - Removed network listening ports : tcp        0      0 *:sane-port                 *:*                         LISTEN      2631/xinetd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : tcp        0      0 localhost.localdomain:10026 *:*                         LISTEN      2987/master
Jun 16 15:20:57 localhost msec: - Removed network listening ports : tcp        0      0 *:ssh                       *:*                         LISTEN      2442/sshd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : tcp        0      0 *:ipp                       *:*                         LISTEN      2427/cupsd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : tcp        0      0 *:ssh                       *:*                         LISTEN      2442/sshd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 *:bootpc                    *:*                                     2267/dhclient
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 *:ipp                       *:*                                     2427/cupsd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 linux.local:ntp             *:*                                     2465/ntpd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 localhost.localdomain:ntp   *:*                                     2465/ntpd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 *:ntp                       *:*                                     2465/ntpd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 *:57527                     *:*                                     2589/avahi-daemon:
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 *:10457                     *:*                                     2267/dhclient
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 *:5353                      *:*                                     2589/avahi-daemon:
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 *:59696                     *:*                                     2830/python
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 *:1900                      *:*                                     2830/python
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 fe80::230:67ff:fe01:ntp     *:*                                     2465/ntpd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 ::1:ntp                     *:*                                     2465/ntpd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 *:ntp                       *:*                                     2465/ntpd
Jun 16 15:20:57 localhost msec: - Removed network listening ports : udp        0      0 *:15766                     *:*                                     2267/dhclient
Jun 16 15:20:57 localhost msec: Security Warning: change in local users found :
Jun 16 15:20:57 localhost msec: -   Added local users : shutterbug
Jun 16 15:20:57 localhost msec: Security Warning: change in local groups found :
Jun 16 15:20:57 localhost msec: -   Added local groups : shutterbug
Jun 16 15:20:57 localhost postfix/pickup[3096]: CA627A0100: uid=0 from=<root>
Jun 16 15:20:57 localhost postfix/cleanup[19259]: CA627A0100: message-id=<20110616202057.CA627A0100@localhost.localdomain>
Jun 16 15:20:57 localhost postfix/qmgr[3097]: CA627A0100: from=<root@localhost.localdomain>, size=7692, nrcpt=1 (queue active)
Jun 16 15:20:57 localhost postfix/pickup[3096]: E28EC9FC5D: uid=0 from=<root>
Jun 16 15:20:57 localhost postfix/cleanup[19259]: E28EC9FC5D: message-id=<20110616202057.E28EC9FC5D@localhost.localdomain>
Jun 16 15:20:57 localhost postfix/qmgr[3097]: E28EC9FC5D: from=<root@localhost.localdomain>, size=6967, nrcpt=1 (queue active)
Jun 16 15:20:58 localhost postfix/local[19273]: CA627A0100: to=<postfix@localhost.localdomain>, orig_to=<root>, relay=local, delay=0.34, delays=0.17/0.07/0/0.1, dsn=2.0.0, status=sent (delivered to mailbox)
Jun 16 15:20:58 localhost postfix/qmgr[3097]: CA627A0100: removed
Jun 16 15:20:58 localhost anacron[5023]: Job `cron.daily' terminated
Jun 16 15:20:59 localhost postfix/local[19274]: E28EC9FC5D: to=<postfix@localhost.localdomain>, orig_to=<root>, relay=local, delay=1.4, delays=0.15/0.02/0/1.2, dsn=2.0.0, status=sent (delivered to mailbox)
Jun 16 15:20:59 localhost postfix/qmgr[3097]: E28EC9FC5D: removed


Thanks for helping on this problem.

Bob
« Last Edit: June 16, 2011, 02:24:30 PM by Snapshot »
Logged
If fishing is interfering
with your business, give
up your business.
Sparse Grey Hackle
(Alfred W. Miller)

Offline muungwana

  • Hero Member
  • *****
  • Posts: 6201
Re: System won't boot after update.
« Reply #14 on: June 16, 2011, 02:29:36 PM »

just to be clear, you have reinstalled and you are having the same problem you have in your previous install?

i asked for the output of your newly installed system.

after a fresh install, why would an update fail on you and not on anybody else? do you have a unique setup? a unique system spec?

what does it the update say when it fails?

try to update from the terminal and see what msgs you will get if any, you can do that by running these commands

apt-get update
apt-get dist-upgrade
Logged
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..
Pages: [1] 2 3 4   Go Up
« previous next »