No it was not - just 444. I added write for the Hobbit user/group.<br><br>It's been 20m and the history.log has not said a thing. I believe it is fixed.<br><br>The grand total data size for the Hobbit user's home directory is 100M - uncompressed. This will be very easy to backup with either method.
<br><br>Thanks a whole lot guys, greatly appreciate the help!<br><br>Josh<br><br><div><span class="gmail_quote">On 10/19/07, <b class="gmail_sendername">Iain Conochie</b> <<a href="mailto:iain@shihad.org">iain@shihad.org
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Josh Luthman wrote:<br>> Stef,<br>><br>> Thanks for the suggestions! I'll keep these in mind when it comes
<br>> time to creating my backups.<br>><br>> For now I deleted the core* files and within a few minutes the<br>> server/bin dir started filling up with the core* files. I looked at<br>> history.log and I see 25165 lines that look like:
<br>><br>> 2007-10-18 17:39:05 Cannot open the all-events file '/home/user/data/hist/allevents'<br>> 2007-10-18 17:39:05 Worker process died with exit code 139, terminating<br>><br>> The log is filled with this pair of lines, over and over (though I
<br>> don't know why the number of lines is odd). What should this<br>> allevents file contain?<br><br>This file contains a list of all event changes, i.e. when a test changes<br>colour. It is the basic history file.
<br><br>Is it writable by your hobbit user?<br><br>Iain<br><br>><br>> Josh<br>><br>> On 10/19/07, *Stef Coene* <<a href="mailto:stef.coene@docum.org">stef.coene@docum.org</a><br>> <mailto:<a href="mailto:stef.coene@docum.org">
stef.coene@docum.org</a>>> wrote:<br>><br>> On Thursday 18 October 2007, Josh Luthman wrote:<br>> > I've only had Hobbit running since last Monday. I have<br>> restarted it twice<br>> > to ensure that my configurations would take place (things like
<br>> changing the<br>> > WWW hostname). I last restarted it yesterday and it has been<br>> running since<br>> > yesterday, so I know if it is restarting it takes more then a<br>> day. I have
<br>> > 40787 total core* files in ~/server and 569364 total core* files in<br>> > ~/server/bin - couldn't possibly have restarted that many times!<br>> Look at the timestamps of these files. Each crash can create a
<br>> core file. So<br>> each visit to the hobbit site, every poll hobbit does, every rrd<br>> update can<br>> create a crash and a core file. I never had a crash/core file,<br>> but in theory
<br>> it can.<br>> We also use vmware so if a hobbit server goes down, I copy the<br>> vmware guest<br>> that I use to deploy new installations, copy over the etc<br>> directory, goes to
<br>> the custumer, pick a computer/desktop/laptop/server, install<br>> vmware player<br>> and hobbit is running again.<br>><br>> > Stef - If you have two Hobbit servers and duplicate your
<br>> actions, why do<br>> > you note your actions? My original plan was to tar the home<br>> directory of<br>> > the hobbit user, but as<br>> I don't have 2 hobbit servers, but more then 20 located for our
<br>> customers.<br>> The bare mimal I need for re-creating the same setup is the<br>> contents of etc<br>> and some extra information I collected during the installation<br>> (hostname,
<br>> network settings, ...).<br>><br>> > "Hobbit User" - I could use rsync and it would make backups though I<br>> > normally don't use rsync as I like to have daily backups, in
<br>> case I make a<br>> > mistake on Monday, the backup is done Tuesday and I catch it on<br>> Wednesday -<br>> > I can revert to Sunday with daily backups. Rsync could have<br>> backed up my
<br>> > problem making it useless in this scenario! I have a scripts<br>> that backup<br>> > necessary components (like databases) and then finally tar with<br>> gzip<br>> > compression and then SCP the file to a remote data center (I
<br>> also use<br>> > public keys to automate this). I have found this works very<br>> well in my<br>> > situation and has saved my life in the case of a MySQL database<br>> crash!
<br>> You don't have to rsync everything in the same way. If you look<br>> at the hobbit<br>> server data, the stuff in the data directory takes op 99% of the<br>> disk space.<br>> And that stuff can be rsync'd and overwritten daily. For the server
<br>> installation, you can also use rsync but do something like this:<br>> rsync -Auhv --delete ~hobbit/server/<br>> <remote>:/backup/hobbit/server-`date +%a`<br>> So every day of the week you will have a new directory so you have
<br>> a history<br>> of 7 days.<br>><br>> > Would it be safe for me to delete these core files and start<br>> working on<br>> > this task from this day forward? What can I use to read these
<br>> core files?<br>> > I noticed they're not text files so I assume there is some bb<br>> utility to<br>> > read them. With the exception of these core* files, I would<br>> expect Hobbit
<br>> > to peak at 200MB which I could do in a ~3 minutes<br>> You can delete the core files, but you should also try to find out<br>> why the are<br>> created. If you use rsync, you can exclude these core files from
<br>> being<br>> rsync'd<br>><br>><br>> Stef<br>><br>> To unsubscribe from the hobbit list, send an e-mail to<br>> <a href="mailto:hobbit-unsubscribe@hswn.dk">hobbit-unsubscribe@hswn.dk
</a> <mailto:<a href="mailto:hobbit-unsubscribe@hswn.dk">hobbit-unsubscribe@hswn.dk</a>><br>><br>><br>><br>><br>><br>> --<br>> Josh Luthman<br>> Office: 937-552-2340<br>> Direct: 937-552-2343
<br>> 1100 Wayne St<br>> Suite 1337<br>> Troy, OH 45373<br>><br>> Those who don't understand UNIX are condemned to reinvent it, poorly.<br>> --- Henry Spencer<br><br><br>To unsubscribe from the hobbit list, send an e-mail to
<br><a href="mailto:hobbit-unsubscribe@hswn.dk">hobbit-unsubscribe@hswn.dk</a><br><br><br></blockquote></div><br><br clear="all"><br>-- <br>Josh Luthman<br>Office: 937-552-2340<br>Direct: 937-552-2343<br>1100 Wayne St<br>
Suite 1337<br>Troy, OH 45373<br><br>Those who don't understand UNIX are condemned to reinvent it, poorly.<br>--- Henry Spencer