Linux Help
guides forums blogs
Home Desktops Distributions ISO Images Logos Newbies Reviews Software Support & Resources Linuxhelp Wiki

Welcome Guest ( Log In | Register )



Advanced DNS Management
New ZoneEdit. New Managment.

FREE DNS Is Back

Sign Up Now
> Remote printing problem becomes total system meltdown, Can't even login
jamespetts
post Feb 11 2009, 05:54 PM
Post #1


Whats this Lie-nix Thing?
*

Group: Members
Posts: 6
Joined: 6-August 04
Member No.: 3,497



At home, there are four computers: study, bedroom, kitchen and parlour. Kitchen and parlour are running Ubuntu Intrepid; bedroom is running Ubuntu Hardy and Study is running Windows XP.

Earlier this evening, a problem was found printing from kitchen to parlour. I had earlier configured cups using the GUI to print from kitchen to parlour without difficulty, so found this odd. I spent a great deal of time trying to solve the problem without success, the problem always appearing to be that the server was refusing permission to access it to the clients, even though the server was configured to allow remote printing and remote administration, the clients' IPs were in the allowed list, all relevant usernames were given permission to print, and it had worked with those exact settings recently before.

I tried to configure the printer from bedroom (I had not previously set up the printer from there), and got exactly the same error. I tried to access the CUPS web configuration on parlour, from bedroom and I got a 403 (I had earlier tried the same from kitchen with the same result). So, on bedroom, I tried to configure the printer through Bedroom's CUPS web interface. I added a printer, and selected the appropriate driver (HP Photosmart D7300 series). I sent it a test page from the web interface, but nothing printed - it was marked perpetually as "processing".

I went to parlour to investigate, and could now not access the CUPS web interface even locally - it appeared that the web server was not giving any sort of response. I tried restarting CUPS from the command line, but got a segmentation fault. Trying to reboot from the command line also gave a segmentation fault. I rebooted from the GUI. The loading bar screen appeared, but there were bizarre artefacts (looking like fragments of the blank loading bar under the Ubuntu logo) next to the live loading bar, which progressed as normal.

I reached the login screen as normal, but any attempt to login just brought the interface back to the login screen again, even with "failsafe terminal" selected as the session. I tried rebooting in failsafe mode from the GRUB menu, and attempted to use the automatic repair tools there (FSCK, XFIX, and DPKG fix), but, on rebooting again, there was no change. I am at a total loss, and very concerned that something quite drastic but utterly incomprehensible has gone wrong. I cannot even access shared NFS folders on parlour from other computers. I should be very, very grateful for any assistance at all, especially as this is my parents' computer that I help to maintain for them and they really do rely on it for a great many things.
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
michaelk
post Feb 12 2009, 07:31 PM
Post #2


Its GNU/Linuxhelp.net
*******

Group: Support Specialist
Posts: 1,797
Joined: 23-January 03
Member No.: 360



No problems mounting or accessing the / partition from a live CD. No obvious errors when looking at the output of the dmesg command?
Go to the top of the page
 
+Quote Post
jamespetts
post Feb 13 2009, 04:08 AM
Post #3


Whats this Lie-nix Thing?
*

Group: Members
Posts: 6
Joined: 6-August 04
Member No.: 3,497



QUOTE (michaelk @ Feb 12 2009, 07:31 PM) *
No problems mounting or accessing the / partition from a live CD. No obvious errors when looking at the output of the dmesg command?


Thank you very much for your help. There are some errors on dmesg when booting from the LiveCD, actually (I am writing this reply from the problem system on the LiveCD now). Here is the section with the errors (I tried to post the full output, but the forum software complained that it was too long):

CODE
[    8.235527] kjournald starting.  Commit interval 5 seconds
[    8.235543] EXT3-fs: mounted filesystem with ordered data mode.
[    8.659624] end_request: I/O error, dev sr0, sector 1431184
[    8.659635] Buffer I/O error on device sr0, logical block 178898
[    9.266496] end_request: I/O error, dev sr0, sector 1431184
[    9.266507] Buffer I/O error on device sr0, logical block 178898
[    9.873350] end_request: I/O error, dev sr0, sector 1431184
[    9.873354] Buffer I/O error on device sr0, logical block 178898
[   10.480213] end_request: I/O error, dev sr0, sector 1431184
[   10.480221] Buffer I/O error on device sr0, logical block 178898
[   11.087082] end_request: I/O error, dev sr0, sector 1431184
[   11.087090] Buffer I/O error on device sr0, logical block 178898
[   11.264216] usb-storage: device scan complete
[   11.264701] scsi 6:0:0:0: Direct-Access     HP       Photosmart D7300 1.00 PQ: 0 ANSI: 2
[   11.274478] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[   11.274674] sd 6:0:0:0: Attached scsi generic sg4 type 0
[   11.518500] kjournald starting.  Commit interval 5 seconds
[   11.518517] EXT3-fs: mounted filesystem with ordered data mode.
[   11.693943] end_request: I/O error, dev sr0, sector 1431184
[   11.693953] Buffer I/O error on device sr0, logical block 178898
[   12.604241] end_request: I/O error, dev sr0, sector 1431184
[   12.604250] Buffer I/O error on device sr0, logical block 178898
[   13.017455] kjournald starting.  Commit interval 5 seconds
[   13.017472] EXT3-fs: mounted filesystem with ordered data mode.
[   13.211187] end_request: I/O error, dev sr0, sector 1431184
[   13.211198] Buffer I/O error on device sr0, logical block 178898
[   14.784902] kjournald starting.  Commit interval 5 seconds
[   14.784918] EXT3-fs: mounted filesystem with ordered data mode.
[   16.924584] ISO 9660 Extensions: Microsoft Joliet Level 3
[   17.069405] ISO 9660 Extensions: RRIP_1991A
[   17.617073] aufs 20080922


Any clues as to what the problem might be from that?

Edit: I have found further reference to "sr0" earlier in the output, which might be of assistance:
CODE
[    5.488463] sr0: scsi3-mmc drive: 4x/40x writer dvd-ram cd/rw xa/form2 cdda tray
[    5.488471] Uniform CD-ROM driver Revision: 3.20
[    5.488607] sr 5:0:0:0: Attached scsi CD-ROM sr0
[    5.491587] sr1: scsi3-mmc drive: 0x/50x cd/rw xa/form2 cdda tray
[    5.491743] sr 5:0:1:0: Attached scsi CD-ROM sr1


Go to the top of the page
 
+Quote Post

Posts in this topic


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st October 2017 - 11:22 PM