/opt/Gooby gone

[techperplexed]

/opt/Gooby gone

[HitsvilleUK]

"Seems others don't have the problem"
Oh dear, they do now. :-(
I just set up one of the German servers and Opt/Gooby is gone on each and every reboot.

[deedeefink]

Nope, I got the newest version using the snippets above and I still have my folder :-) It just happened one time

[TechPerplexed]

Oh that is odd.... does it only happen after a reboot (not after a manual system clean)? Is it random or does it follow a pattern? I just rebooted and unfortunately I can't reproduce this....... mine came back just fine.

So the rest of the cron goes through all right? Mount coming back, services started, containers working?

[Coxeroni]

To be honest I don't know what causes it and when, just saw that rclean does something like that.
I also had some issues with the mounts not coming up and reboots took several minutes. The problem with the mounts was also caused by changes in some of the scripts which were obviously automatically updated but caused trouble. I know this is all very unspecific and probably doesn't help, but acutally I don't know what does what and when so I cannot pin point where to problem is ;)

Did I get that right, that in principle the script deletes itself and if the clone from GitHub fails rclean is not present to be run at reboot anymore and so Gooby won't be present unless installed by hand?

Btw I disabled rclean in cron as a temporary fix and I just run some of the commands by hand if needed.

[TechPerplexed]

Yes, that is correct - the script will update Gooby and in order to do so, GitHub needs to delete the folder altogether and recreate it. You could change the script not to update Gooby and leave the cron as is... in some ways the cron is necessary to make sure everything comes up in the right order (mount first, containers, next, etc).

You can just edit the file sudo nano /opt/Gooby/scripts/cron/rclean.sh and comment out the relevant lines like this:

# sudo rm -r /opt/Gooby
# sudo git clone -b master https://github.com/TechPerplexed/Gooby /opt/Gooby 
# sudo chmod +x -R /opt/Gooby/install
# sudo chmod +x -R /opt/Gooby/menus
# sudo chmod +x -R /opt/Gooby/scripts/cron
# sudo rsync -a /opt/Gooby/install/gooby /bin
# sudo chmod 755 /bin/gooby

That way Gooby only updates when you run the update function from the menu :)

[Coxeroni]

Good idea, that change I would need to perform again after the update though, but I that sounds doable. Still, I would want to know what goes wrong in the first place...

[TechPerplexed]

Oh gosh yes, me too!! I haven't heard anyone complain about it though, so I'll leave this open for a few days to see if others chime in having the same problem (or not). It's difficult to troubleshoot what you can't reproduce at all....

[TechPerplexed]

Seems others don't have the problem Coxeroni, and in the past few days I have been rebooting at least a million times (ok, maybe not quite THAT often, but it feels like it...) and it came back each and every time. I will close it for now and hope you find out what's causing yours to misbehave! Of course you can always add more information to this thread, it won't be locked :)

[TechPerplexed]

Ha! Ok, for the time being I have disabled the automatic upgrade process (please update Gooby to trigger the update) :)

Working on a failsafe system to update the menu reliably - to be continued!

[deedeefink]

Same just happened to me :-(

[TechPerplexed]

Hmm, that's even stranger... because I disabled the automatic update for now. Please reinstall

sudo git clone -b master https://github.com/TechPerplexed/Gooby /opt/Gooby
sudo chmod +x -R /opt/Gooby/install
sudo chmod +x -R /opt/Gooby/menus
sudo chmod +x -R /opt/Gooby/scripts/cron
sudo rsync -a /opt/Gooby/install/gooby /bin
sudo chmod 755 /bin/gooby

And then run a system clean and/or reboot. Does it still happen??