View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 12 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sun Feb 19, 2012 11:53 am 
Offline
Joined: Mon Feb 27, 2006 10:39 pm
Posts: 48
My LinHES box is having a problem where it won't respond, no DVI out, no ssh in. The only thing I can do is hold down the power button to turn it off and restart it. This is a fresh install of LinHES 7.2, I ended up accidentally formatting my LinHES 6.4 after the upgrade failed, and I had to make a CD.

I have tried to look at the messages file, but it is missing from my box. Only log files that have been written to today (system failed sometime around 5:25 this morning, it was in the middle of a recording ) are,

dmesg.log
fluxbox.log
network.init
network.init.error
Xorg.0.log

Dmesg.log appears to have been just from my boot as it is only 40K

Any suggestions on where I can look to see why my box is crashing?


Last edited by huntermcdole on Mon Feb 20, 2012 6:25 pm, edited 1 time in total.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 19, 2012 12:30 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
Based on that collection of log files it sounds like some kind of startup problem with X. What's in the network.init* files? (they're usually small) and what are the last 20 or so lines from dmesg.log? Finally, are there any errors (search for lines that start with '(EE)') in the Xorg.0.log?


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 19, 2012 12:39 pm 
Offline
Joined: Mon Feb 27, 2006 10:39 pm
Posts: 48
Here you go

network.init.error
Code:
dhcpcd[747]: version 5.2.8 starting
dhcpcd[747]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd[747]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd[747]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
dhcpcd[747]: eth0: rebinding lease of 192.168.50.114
dhcpcd[747]: eth0: sending REQUEST (xid 0x5a642403), next in 4.11 seconds
dhcpcd[747]: eth0: acknowledged 192.168.50.114 from 192.168.50.1
dhcpcd[747]: eth0: checking for 192.168.50.114
dhcpcd[747]: eth0: sending ARP probe (1 of 3), next in 1.85 seconds
dhcpcd[747]: eth0: sending ARP probe (2 of 3), next in 1.65 seconds
dhcpcd[747]: eth0: sending ARP probe (3 of 3), next in 2.00 seconds
dhcpcd[747]: eth0: leased 192.168.50.114 for 5184000 seconds
dhcpcd[747]: eth0: adding IP address 192.168.50.114/24
dhcpcd[747]: eth0: adding route to 192.168.50.0/24
dhcpcd[747]: eth0: adding default route via 192.168.50.1
dhcpcd[747]: eth0: writing lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
dhcpcd[747]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
dhcpcd[747]: forking to background
dhcpcd[747]: forked to background, child pid 769


network.init
Code:
Computing interface groups: .. 2 interfaces found
Starting group 0/virtual (1 interfaces)
        Starting lo:  'lo' is already up SKIPPED
Starting group 1/realphys (1 interfaces)
        Starting eth0: .....OK
Processing /etc/net/vlantab: empty.



dmesg.log
Code:
[    9.691923] msp3400 2-0040: msp3400 supports radio, mode is autodetect and autoselect
[    9.752078] tuner 2-0061: Tuner -1 found with type(s) Radio TV.
[    9.760859] tuner-simple 2-0061: creating new instance
[    9.760864] tuner-simple 2-0061: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles))
[    9.766016] ivtv1: Registered device video1 for encoder MPG (4096 kB)
[    9.766121] ivtv1: Registered device video33 for encoder YUV (2048 kB)
[    9.766211] ivtv1: Registered device vbi1 for encoder VBI (1024 kB)
[    9.766293] ivtv1: Registered device video25 for encoder PCM (320 kB)
[    9.766298] ivtv1: Initialized card: Hauppauge WinTV PVR-250
[    9.766636] ivtv: End initialization
[    9.793775] nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    9.793790] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:ow$
[    9.794406] NVRM: loading NVIDIA UNIX x86 Kernel Module  173.14.30  Thu Apr 14 08:47:14 PDT 20$
[    9.882257] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[   10.082134] ivtv0: Encoder revision: 0x02060039
[   10.410228] ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
[   10.437784] ivtv1: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
[   10.637356] ivtv1: Encoder revision: 0x02060039
[   10.637497] ivtv1: Decoder revision: 0x02020023
[   13.734292] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[   14.620076] EXT3-fs (sda1): using internal journal
[   14.732270] EXT3-fs: barriers not enabled
[   14.732916] kjournald starting.  Commit interval 5 seconds
[   14.733301] EXT3-fs (sda3): using internal journal
[   14.733307] EXT3-fs (sda3): mounted filesystem with ordered data mode
[   14.812716] Adding 1028092k swap on /dev/sda2.  Priority:-1 extents:1 across:1028092k


Xorg.o.log Error
Code:
[    30.726] (EE) Failed to load module "kbd" (module does not exist, 0)
[    30.726] (EE) Failed to load module "mouse" (module does not exist, 0)
[    32.822] (EE) Failed to load module "kbd" (module does not exist, 0)
[    32.822] (EE) No input driver matching `kbd'
[    32.823] (EE) Failed to load module "mouse" (module does not exist, 0)
[    32.823] (EE) No input driver matching `mouse'


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 19, 2012 1:39 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
Good news first, dmesg and network.init output looks OK.

On the other hand, the fact that network.init.error isn't empty raises an eyebrow even though nothing there looks exciting. Mine is empty, but then again I'm not using DHCP and most of the messages in yours are DHCP related. Probably not a problem...

The X errors look more serious, since it's not even finding core drivers. Both kbd and mouse should be there if X is installed... Does this show anything?
Code:
pacman -Qs xf86-input


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 19, 2012 1:54 pm 
Offline
Joined: Mon Feb 27, 2006 10:39 pm
Posts: 48
local/xf86-input-evdev 2.6.0-4 (xorg-drivers xorg)
X.org evdev input driver


Now I am using a USB Mouse and Keyboard in one combo, would that change it?


Top
 Profile  
 
PostPosted: Mon Feb 20, 2012 1:30 pm 
Offline
Site Admin
Joined: Fri Jun 11, 2004 7:58 am
Posts: 507
Log files have moved to /var/log/messages/$DATE
There may be something of interest in the other log files


Top
 Profile  
 
 Post subject: Re:
PostPosted: Mon Feb 20, 2012 2:04 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
huntermcdole wrote:
local/xf86-input-evdev 2.6.0-4 (xorg-drivers xorg)
X.org evdev input driver

Now I am using a USB Mouse and Keyboard in one combo, would that change it?

I'm using a combined wireless keyboard/touchpad myself, so no it doesn't matter. It's not the physical devices so much as the systems logical view of it.

Unless the packaging has changed radically (I'm still on 6.04), it looks like a lot of stuff isn't installed on your system.

BTW - after so many years on the old system the new look seems very strange. Especially the lower contrast, I'm hoping that there are some user settings that will let me customize it...


Top
 Profile  
 
PostPosted: Mon Feb 20, 2012 6:23 pm 
Offline
Joined: Mon Feb 27, 2006 10:39 pm
Posts: 48
@TJC
What is weird I have no issues w/ my mouse and Keyboard... but it did freeze/lockup last night @ around 11:24, during 2 recordings, it was 24:25 minutes in, I think that was what the other recording was also. I would of stayed on 6.04 but I was having some issues, one of which was I could no longer access the LinHES Service menu, also random crashes of mythfrontend.. which I still have issues w/ mythfrontend crashing after leaving recordings sometimes.

Biggest issue I have had so far w/ 7.2 other than the lockup/freezes is the installer only wanted to do 800x600 and my LCD tv won't show that resolution on the screen... I had to quickly pull up an xterm in the install and change the resolution to 1900xsomething, and working w/ nvidia-setup was a pain when the ok button is off the screen....

I did a smartctl -t short /dev/sda on my box
Code:
smartctl 5.41 2011-06-09 r3365 [i686-linux-2.6.39-LinHES] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.11
Device Model:     ST3500320AS
Serial Number:    9QM39Z4C
LU WWN Device Id: 5 000c50 00cc2c7af
Firmware Version: SD15
User Capacity:    500,107,862,016 bytes [500 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Mon Feb 20 17:44:38 2012 MST

==> WARNING: There are known problems with these drives,
AND THIS FIRMWARE VERSION IS AFFECTED,
see the following Seagate web pages:
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x82)   Offline data collection activity
               was completed without error.
               Auto Offline Data Collection: Enabled.
Self-test execution status:      (  89)   The previous self-test completed having
               the electrical element of the test
               failed.
Total time to complete Offline
data collection:       (  642) seconds.
Offline data collection
capabilities:           (0x7b) SMART execute Offline immediate.
               Auto Offline data collection on/off support.
               Suspend Offline collection upon new
               command.
               Offline surface scan supported.
               Self-test supported.
               Conveyance Self-test supported.
               Selective Self-test supported.
SMART capabilities:            (0x0003)   Saves SMART data before entering
               power-saving mode.
               Supports SMART auto save timer.
Error logging capability:        (0x01)   Error logging supported.
               General Purpose Logging supported.
Short self-test routine
recommended polling time:     (   1) minutes.
Extended self-test routine
recommended polling time:     ( 118) minutes.
Conveyance self-test routine
recommended polling time:     (   2) minutes.
SCT capabilities:           (0x103b)   SCT Status supported.
               SCT Error Recovery Control supported.
               SCT Feature Control supported.
               SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   117   099   006    Pre-fail  Always       -       118167943
  3 Spin_Up_Time            0x0003   097   095   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       49
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   073   060   030    Pre-fail  Always       -       25910110714
  9 Power_On_Hours          0x0032   064   064   000    Old_age   Always       -       31793
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       1
 12 Power_Cycle_Count       0x0032   100   037   020    Old_age   Always       -       49
184 End-to-End_Error        0x0032   001   001   099    Old_age   Always   FAILING_NOW 143
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   098   000    Old_age   Always       -       61
189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -       310
190 Airflow_Temperature_Cel 0x0022   059   058   045    Old_age   Always       -       41 (Min/Max 38/42)
194 Temperature_Celsius     0x0022   041   042   000    Old_age   Always       -       41 (0 15 0 0)
195 Hardware_ECC_Recovered  0x001a   030   015   000    Old_age   Always       -       118167943
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 77 (device log contains only the most recent five errors)
   CR = Command Register [HEX]
   FR = Features Register [HEX]
   SC = Sector Count Register [HEX]
   SN = Sector Number Register [HEX]
   CL = Cylinder Low Register [HEX]
   CH = Cylinder High Register [HEX]
   DH = Device/Head Register [HEX]
   DC = Device Command Register [HEX]
   ER = Error register [HEX]
   ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 77 occurred at disk power-on lifetime: 31775 hours (1323 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 81 87 80 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 02      13:09:09.374  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      13:09:09.371  IDENTIFY DEVICE
  00 00 00 00 00 00 00 06      13:09:09.220  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 02      13:09:04.223  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      13:09:04.220  IDENTIFY DEVICE

Error 76 occurred at disk power-on lifetime: 31775 hours (1323 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 81 87 80 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 02      13:09:09.371  IDENTIFY DEVICE
  00 00 00 00 00 00 00 06      13:09:09.220  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 02      13:09:04.223  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      13:09:04.220  IDENTIFY DEVICE
  00 00 00 00 00 00 00 06      13:09:04.069  NOP [Abort queued commands]

Error 75 occurred at disk power-on lifetime: 31775 hours (1323 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 81 87 80 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 02      13:09:04.223  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      13:09:04.220  IDENTIFY DEVICE
  00 00 00 00 00 00 00 06      13:09:04.069  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 02      13:09:04.050  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      13:09:03.955  IDENTIFY DEVICE

Error 74 occurred at disk power-on lifetime: 31775 hours (1323 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 81 87 80 e0

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  ec 00 00 00 00 00 a0 02      13:09:04.220  IDENTIFY DEVICE
  00 00 00 00 00 00 00 06      13:09:04.069  NOP [Abort queued commands]
  a1 00 00 00 00 00 a0 02      13:09:04.050  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      13:09:03.955  IDENTIFY DEVICE
  35 00 18 ff ff ff ef 00      13:09:03.955  WRITE DMA EXT

Error 73 occurred at disk power-on lifetime: 31775 hours (1323 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 71 04 81 87 80 e0  Device Fault; Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  a1 00 00 00 00 00 a0 02      13:09:04.050  IDENTIFY PACKET DEVICE
  ec 00 00 00 00 00 a0 02      13:09:03.955  IDENTIFY DEVICE
  35 00 18 ff ff ff ef 00      13:09:03.955  WRITE DMA EXT
  35 00 e8 ff ff ff ef 00      13:09:03.755  WRITE DMA EXT
  35 00 b0 ff ff ff ef 00      13:09:03.733  WRITE DMA EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: electrical failure 90%     31793         0

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.



@Jams
I don't have a messages folder :(

Code:
[hunter@mythtv log]$ ls -all
total 732
drwxr-xr-x  5 root   root     4096 Feb 20 09:44 .
drwxr-xr-x 13 root   root     4096 Feb 11 14:35 ..
-rw-r--r--  1 root   root    40179 Feb 20 09:44 dmesg.log
-rw-r--r--  1 mythtv mythtv  14957 Feb 20 09:52 fluxbox.log
drwxr-xr-x  2 http   http     4096 Feb 19 15:53 lighttpd
-rw-r--r--  1 root   root   249920 Feb 11 14:40 mv_debug.log
-rw-r--r--  1 mysql  root        0 Feb 11 14:41 mysqld.log
drwxr-xr-x  2 mythtv mythtv   4096 Feb 18 15:53 mythtv
-rw-r--r--  1 root   root    28390 Feb 11 14:39 mythvantage_install.log
-rw-r--r--  1 root   root      233 Feb 20 09:44 network.init
-rw-r--r--  1 root   root     1163 Feb 20 09:44 network.init.error
-rw-r--r--  1 root   root    18943 Feb 12 18:35 pacman.log
drwxr-xr-x  3 root   root     4096 Feb 19 15:53 samba
-rw-r--r--  1 mythtv root      316 Feb 20 10:39 smolt.update
-rw-r--r--  1 root   root   169110 Feb 20 10:43 Xorg.0.log
-rw-r--r--  1 root   root   168910 Feb 19 21:06 Xorg.0.log.old
[hunter@mythtv log]$


Top
 Profile  
 
PostPosted: Mon Feb 20, 2012 7:00 pm 
Offline
Site Admin
Joined: Fri Jun 11, 2004 7:58 am
Posts: 507
I meant to say /var/log/$DATE

But as you don't have that either, I would say that rsyslog is not installed or not running.


Top
 Profile  
 
PostPosted: Fri Apr 13, 2012 11:00 am 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1532
Location: California
jams wrote:
I meant to say /var/log/$DATE

But as you don't have that either, I would say that rsyslog is not installed or not running.

I am running 7.2 and I do not appear to that those directories. "ps auxw | grep rsyslog" yields the following
Code:
ps auxw | grep rsyslog
root       941  0.0  0.0   1776   344 ?        Ss   09:21   0:00 runsvdir -P /set ./run: access denied?runsv rsyslog: fatal: unable to start ./run: access deniee to start ./run: access denied?runsv rsyslog: fatal: unable to start ./run: acc
root       966  0.1  0.0   1632   320 ?        Ss   09:21   0:03 runsv rsyslog
root      7694  0.0  0.0   4300   832 pts/1    S+   09:56   0:00 grep rsyslog


Any advise would be greatly appreciated.

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.


Top
 Profile  
 
PostPosted: Fri Apr 13, 2012 1:10 pm 
Offline
Joined: Fri Jul 21, 2006 11:12 pm
Posts: 1194
Location: SC
http://linhes.org/issues/819


Top
 Profile  
 
PostPosted: Fri Apr 13, 2012 1:21 pm 
Offline
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1532
Location: California
brfransen wrote:
http://linhes.org/issues/819

That fixed it, thanks!

_________________
Marc

The views expressed are my own and do not necessarily reflect the views of my employer.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 12 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 28 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu