PDA

View Full Version : terminal commands



trailer8713
16th April 2008, 04:20 AM
Can any one suggest some terminal commands to find and fix problems. My fedora 8 desktop has started to act up just shuts down crash doesn't go thru normal shut down usually 2 times a day. Skype will not load, K3B shuts down @ write, some times for no reason I know of the screen just goes white and shuts down.
Apt-get check all is good
apt-get --fix- broken nothing to due
Last time it did this was after the F8 upgrade and I think Beryl and compiz were clashing that was fixxed. please help there have got to be some good commands to find and fix whatis going on.
Thank you

Seve
16th April 2008, 05:34 AM
Hello:
Try

tail -f /var/log/messages >> /home/username/new.log

This will / should produce a log file(new.log) in your home directory with some clues as to what is happening at the time of the crashes.

Seve

trailer8713
16th April 2008, 01:42 PM
[root@Craig craig]# tail -f /var/log/messages >> /home/username/new.log
bash: /home/username/new.log: No such file or directory
[root@Craig craig]# -f /var/log/messages >> /home/username/new.log
bash: /home/username/new.log: No such file or directory

I am unable to get the desired response. please could you give me further direction.
Thank you

pete_1967
16th April 2008, 01:47 PM
replace the 'username' with your account name (e.g. /home/trailer8713/newlog)

If you're not sure, open your terminal (console) and type `pwd` and you'll see the correct path.

scottro
16th April 2008, 01:48 PM
I believe you need root privilege to view /var/log/messages. Try doing su to root then running the command. (Then, still as root do chown craig /home/craig/new.log--or just let the log file write to /home/root.)

trailer8713
16th April 2008, 02:04 PM
[root@Craig craig]# tail -f /var/log/messages >> /home/craig/new.log

that is what I did does that look right , the curser is just flashing under that message. didn't give me
[root@Craig craig]# on the next line just flashing curser

ghost_ryder35
16th April 2008, 02:27 PM
you could also manually go to


su -
password prompt
cd /var/log/
gedit messages

then click file, save as, and save it to your desktop, then post the file up here for us to review

alternativly to this if you have set your self up as a "sudoer" then you could go this method,



sudo gedit /var/log/messages
password prompt

then click file, save as, and save it to your desktop, then post the file up here for us to review

Hlingler
16th April 2008, 02:38 PM
[root@Craig craig]# tail -f /var/log/messages >> /home/craig/new.log

that is what I did does that look right , the curser is just flashing under that message. didn't give me
[root@Craig craig]# on the next line just flashing curserThat's correct: the "-f" option means "follow", meaning keep following new entries to the original file and continue to write (append) to the new copy file. So the job stays alive until you kill it with CTL-c.

V

P.S. You can temporarily stop the job and get back to the prompt with:
CTL-z
Then you can put the job in the background and let it run with:
bg %1
The job will run in the background forever, though, until you manually kill it.

ghost_ryder35
16th April 2008, 02:46 PM
That's correct: the "-f" option means "follow", meaning keep following new entries to the original file and continue to write (append) to the new copy file. So the job stays alive until you kill it with CTL-c.

V

P.S. You can temporarily stop the job and get back to the prompt with:
CTL-z
Then you can put the job in the background and let it run with:
bg %1
The job will run in the background forever, though, until you manually kill it.
good to know I didnt realize that. thanks for the FYI

trailer8713
16th April 2008, 05:06 PM
I tryed to copy and paste the original, I guess I didn't post before going back the home tried to reaccess it.
Log had i believe 3 days of info.this is what I have now to post. is this what you mean.
Apr 16 07:33:19 Craig dnsmasq[2337]: using nameserver 192.168.11.1#53
Apr 16 07:33:21 Craig avahi-daemon[2357]: Registering new address record for fe80::219:21ff:fedb:4060 on eth0.*.
Apr 16 07:33:43 Craig kernel: npviewer.bin[2946]: segfault at 78 rip 2aaab5ea65cd rsp 7fffd8418400 error 4
Apr 16 07:33:43 Craig kernel: plugin-config[2939]: segfault at 78 rip 2aaab469c5cd rsp 7fffb2efdde0 error 4
Apr 16 07:38:30 Craig nmbd[2234]: [2008/04/16 07:38:30, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
Apr 16 07:38:30 Craig nmbd[2234]: *****
Apr 16 07:38:30 Craig nmbd[2234]:
Apr 16 07:38:30 Craig nmbd[2234]: Samba name server CRAIG is now a local master browser for workgroup ZIEGELHOME on subnet 192.168.122.1
Apr 16 07:38:30 Craig nmbd[2234]:
Apr 16 07:38:30 Craig nmbd[2234]: *****
It doesn't appear to be updating, I don't know this is new to me.

ghost_ryder35
16th April 2008, 05:27 PM
i think the best thing to do in your situation is wait for the message to reappear and then check out your log files and look for messages around the time you recieved the message that you need to shutdown.

trailer8713
16th April 2008, 05:50 PM
I don't get any messages just shuts down

Hlingler
17th April 2008, 12:17 AM
This sounds suspiciously like a hardware problem, but that's just a guess at this point.

Suggestion: The next time this happens, boot into runlevel 3: stop the bootloader at the blue screen, and add the number 3 (also add a space before 3) to the end of the boot line for your favorite kernel. You will boot into a text terminal, but all services, network connections, etc. should be up and working, only difference is no GUI/desktop because X-server is not started.

Log into the terminal session, and review files: /var/log/messages; ~/.xsession-errors; /var/log/Xorg.0.log. You will need root-user privileges to read the files in /var/log/. Look towards the end of the files for clues. See if anything jumps out.

V