Fog server keeps going down

[cml]

You can set memory allocation in VMWare, in the VM properties go to the resources tab, and click on memory.

You can either reserve all memory, or a set amount.

[szecca1]

@Wayne-Workman I just got into work today and this morning the fog server was still up and running after the memory upgrade to 6 GBs. I can still do that if you’d like because I would hate to see your hard word go to waste. Let me know if you want me to do that

[szecca1]

@cml Thank you I saw this right before I upgraded the memory but didn’t know what to do and didn’t want to mess with something I didn’t understand. The memory upgrade seems to have fixed the issue for now and I will keep an eye on it but do you think I should do this anyways?

[Wayne Workman]

@cml Thank yo ufor the screen shot! I only have Hyper-V & KVM experience, glad someone could give a VMWare screenshot!

@szecca1 Yes please go ahead and setup the crontab event. Because the server is still online today - we know your issue is memory related, and the output from the below scheduled script will help you in the future… Keep in mind - the 6 gigs of RAM may not have fixed it, it may only have lengthened the amount of time between crashes…

[szecca1]

@Wayne-Workman

This is what I am getting when I typed that path in. Am I doing something wrong?

[Wayne Workman]

@szecca1 The path is /root/ the filename is monitor.sh

You create the file. I made it from scratch. You can create it with Vi. Like vi /root/monitor.sh

I suppose you can put the script anywhere you like.

[szecca1]

@Wayne-Workman Hey after I am done typing the script how do I save it?

[szecca1]

@Wayne-Workman I’m sorry I am having a difficult time doing this, so I’m just going to skip it unless you have more instructions on how to do this.

[Wayne Workman]

@szecca1 https://wiki.fogproject.org/wiki/index.php/Vi

Also - use putty and just copy / paste. No need to type all that out.

In Putty, you can copy by selecting the text and then right clicking anywhere on the window.
In Putty, you can paste by simply putting the cursor where you want your text to go, and then right click anywhere on the window.

[szecca1]

@Wayne-Workman Thank you but clearly I did something wrong. This is my output when I followed your instructions

[Wayne Workman]

@szecca1 The cat command just outputs the contents of a file for viewing.

You run executibles in Linux with ./

Like ./installfog.sh ?

Try to run the script you just wrote. Like this:
cd /root
./monitor.sh
then output the contents of the log using the cat command.
cat /root/monitor.log

You can also look at the log using vi…
vi /root/monitor.log

[szecca1]

@Wayne-Workman I may have found my problem but not sure how to fix it

[Wayne Workman]

@szecca1 That’s not a big deal. What gets ran is what is stored on the disk.

Can you run the script? Is there output in the log?

[szecca1]

@Wayne-Workman No I tried to see if the file was in the /root folder and its not so i wanted to make sure that wasn’t a problem. I’ll just recreate it again

[Wayne Workman]

@szecca1 You’re using Fedora right?

Did you create the crontab event as root? the crontab -e command will create a cron event and run as the user who created the event, meaning, not created using root, no permission to the /root directory.

[szecca1]

@szecca1 I dont know what I am doing wrong but when I type /root then ls the file is not there and I continue to go back and resave it and still nothing

[Wayne Workman]

@szecca1 Switch to the root user like this: su root and then create the crontab event.

Apologies for not saying that earlier. I do everything as root.

[szecca1]

@Wayne-Workman apparently I don’t have the password for root

[szecca1]

@Wayne-Workman I was just doing everything through sudo and my password

[george1421]

For better or worse here, I have to be the voice of reason: At some point (in the near future) you have to make a decision to continue down the path to try to fix this install, or just abandon it and spin up a new fog instance and manually copy the files across.

IMO something is botched with this OS install. This system should not become unavailable like this. How much effort are you going to expend on trying to revive this system, where spinning up a new OS and fog install can be done in about 30 minutes.