Tiny Core Linux
General TC => General TC Talk => Topic started by: remus on January 12, 2012, 06:51:56 PM
-
Hi all,
I've created a remastered TC Boot CD that has samba and openssh integrated.
Samba is setup with one user (admin) who can access one share (funding)
Its been working great in VM Workstation testing at home for weeks off an iso file
Its been running from a boot cd on an old P4 machine for 3 days just fine.
I'm using a 20GB hard drive for the samba share.
Just yesterday, I noticed that the funding share was no longer available and I could not ping the computer, its ip address on our LAN is 10.1.1.205. I could not access the machine via ssh
As everything runs off a boot cd, I just hit the reset button on the computer and it still would not work.
I've just realized that each time I reboot the machine I loose any logs, that might hold helpful information.
I'm considering installing the logrotate extension, and getting it to email me with logs each day.
But that wont help if the machine loose's its ip again.
Perhaps I should make /var/log path persistant some how, i'd appreciate any suggestions about how to proceed.
-
Instead of just hitting the reset button, try troubleshooting at the console.
-
Will do,
It was hooked up with ONLY a power and network cable, I've got it setup now with mouse, keyboard and monitor as well.
What ever the problem was, seems to have fixed itself over night, I've just hooked it all backup and and its working for now.
I'm hoping that it was a hardware fault. At least now I can troubleshot from the console.
-
You might want to check and turn off the power saving options in the BIOS.
It might be going into suspend mode.
-
Hi remus
Another member recently reported having problems with TC4.x and Samba (3.6.1).
http://forum.tinycorelinux.net/index.php/topic,12276.msg66025.html#msg66025 (http://forum.tinycorelinux.net/index.php/topic,12276.msg66025.html#msg66025)
-
I really wish I had taken the time yesterday to plug in a monitor + keyboard to have a look at what was happening. I'm really busy at the community centre and had to crack on with what I was doing.
You might want to check and turn off the power saving options in the BIOS.
Thats a good idea, I know the settings you are talking about.
Another member recently reported having problems with TC4.x and Samba (3.6.1).
Thanks for the link Rich, I'm going to test that problem on VM Workstation over the weekend, and again on the testing server at work on Monday.
-
Hi remus
If it happens again, try running top. It will probably show who is hogging all the RAM and/or CPU cycles.
-
Hi Rich,
Thanks for the advice, I left top running on a terminal on that machine before leaving work yesterday, I hope that if the machine freeze's and wont respond to input, I'll at least be able to see what was using ram/cpu before something went wrong.
Its just occurred to me, that I could have done a "tail -f /var/logmessages" in another terminal, which might have been very useful as well.
I've found a few interesting pages about the top command I thought I might share.
- 15 practical top command examples http://www.thegeekstuff.com/2010/01/15-practical-unix-linux-top-command-examples/ (http://www.thegeekstuff.com/2010/01/15-practical-unix-linux-top-command-examples/)
- How to capture the unix top command to a file http://www.thegeekstuff.com/2009/10/how-to-capture-unix-top-command-output-to-a-file-in-readable-format/ (http://www.thegeekstuff.com/2009/10/how-to-capture-unix-top-command-output-to-a-file-in-readable-format/)