50GB is ridiculous, yes that's your problem! No, it doesn't "munch" itself, just make space and it will be fine (unless you've been screwing with things trying to get it working!)
It is perfectly safe to delete the log files, it will just create new ones. However, you need to read the log first and find out what is bloating it, sounds like you have an underlying issue.
Go to a terminal shell
less /var/log/pluto/20_LaunchOrbiter.sh.log and start paging through. Note I quick way to get to the end is hit SHIFT-F which starts "tailing" the end of the log file, then hit CTRL-C so that you can page up and read backwards through the log file.
When ready to delete it, at the shell type
sudo rm /var/log/pluto/20_LaunchOrbiter.sh.log and then enter your linuxmce password when it prompts
You will probably find /var/log/pluto/20_LaunchOrbiter.sh.log.1/2/3 etc files as well that you can delete
Nope. Deleting it alone didn't fix the system, there are other corrupted items. After completing my investigation and fix of my Core, I'll get back and post the problem source, symtoms, and avoidance for next time. I want to do this because I want to be sure and post the correct information, so as not to confuse anyone on the forum.
Thanks,
Charles
Well, I said that I would get back so here it is. This thread probably could have been avoided if I knew more about what occurred. Comments later, but please be kind.
I have had a very good LinuxMCE 810 Alpha2-Latest system running for several months complete with several Windows Orbiters, an ASUS diskless MD with DVD drive for ripping, MCE Remote and a bluetooth dongle. I also have a CM11 for x10 on the Core's COM1, a Bluecherry PVR-143 for Outdoor Cameras, 1 IP D-Link camera connected to the my home networks LAN of which the Core's External LAN is connected to for Internet access. The Internal LAN of the Core connects to a AirLink 101 wireless router used as a switch only, (wired and wireless), that connects the MD's ethernet and a newly added WebDT 366 WebOrbiter using the wireless portion of the Core's Internal LAN's switch, all working great.
The Core's Firewall is presently disabled so that my home network devices such as IP Cameras, Windows LinuxMCE Orbiters can be found by LinuxMCE and so I can HTTP into the WebAdmin of my Core from any Computer on my existing home network. I am still presently hardware fire-walled with my Linksys Router to my DSL Modem.
All that being said, I believe that I could have "Drove a Stake" through the heart of my Core unknowingly. In my shop, which also has Internet access from my Home LAN (of which My system's Core can see), I was helping a friend set up a new LinuxMCE Core. I, not thinking, connected his new proposed Core's External LAN, to my network for access to updates for Kubuntu 810 and then, of course, to install LinuxMCE-Alpha2-Latest from the web. All went well until his Core's installation was setting itself up (final parts of install) and seemed to be fighting to get the Core's Internal OnScreen Orbiter #20 created. It never happened. It seemed to be looping a we gave up because it was 2 am and had enough. I didn't unplug it or shut it down. The next day, gone to a friend's for dinner, about 24hrs later, I discovered that my Core's OnScreen Orbiter was processing extreamly slow. Not knowing what the hell was happening, I finally managed to get the Orbiter's screen to get to the Reset Core button, and execute that command.
When my Core restarted, I was presented with the AV-Wizard on my Core, as if it didn't have the #20 Orbiter anymore. Also it was running very slow and then couldn't get anywhere very fast at all. I had to wait until the next morning to ask my daughter if there were any messages on the MD last night because I knew they were watching a Video on it. She said that during the movie a box popped up saying something about "running out of disk space or disk full", she wasn't sure.
If I would have been home and I was watching and saw this message this would have made me snap and look into it immediatly, but I was gone and things were taking a turn for the worse as both Cores, (I suspect), were doing it to each other and probably no one got kissed before. Now, an already too long story, after the help and suggestions from you guys on the forum, I found the log file, 20_LaunchOrbiter.sh.log at 50 gig and filling up my small OS drive. I have completed New-Install on a much larger drive.
Now for all of you who have helped me in the past, it already hurts if I did this to myself, but the question remains, Did I Cause This? I mean, did the 2 Cores on the same network stop the New install from completing at the #20 OnScreenOrbiter creation and cause my Core to corrupt it's #20 OnScreenOrbiter consequently filling up it's log? I have been aware that you don't need or use 2 Cores, I would have disconnected my system from the network to set up my friends new Core if I would have just realized what I was setting myself up for.
Allright, let me have it...
Thanks,
Charles
