When I will start VAOC I get this error:Application error: a client-side exception has occurred (see

How can I fix this?
No description
14 Replies
miklschmidt
miklschmidt3w ago
debug zip
c00ki3 vc4 300 IDEX
Debug.zip is in configurator. Can Not do it, Same Error
c00ki3 vc4 300 IDEX
I think I will do a fresh install
miklschmidt
miklschmidt3w ago
can't use this, that's klipper. You can get the configurator log from ~/printer_data/log/ratos-configurator.log you could also just open the browser console and show me what it says
c00ki3 vc4 300 IDEX
here you are
miklschmidt
miklschmidt2w ago
Looks like you've installed mooncord? for some reason there's a ton of errors about a mooncord.log not existing in printer_data/logs try this:
touch ~/printer_data/logs/mooncord.log
sudo systemctl restart ratos-configurator
touch ~/printer_data/logs/mooncord.log
sudo systemctl restart ratos-configurator
c00ki3 vc4 300 IDEX
I am at work now. I have uninstalled mooncord days ago. Maybe this is the Problem
miklschmidt
miklschmidt2w ago
actually, it's probably a symlink to a non-existent file so we should prolly remove it first (modifying the commands.. sec) So to start with, show me the output of this
ls -la ~/printer_data/logs
ls -la ~/printer_data/logs
then to fix:
rm -f ~/printer_data/logs/mooncord.log
touch ~/printer_data/logs/mooncord.log # This creates a new empty file, skip if you don't use mooncord
sudo systemctl restart ratos-configurator
rm -f ~/printer_data/logs/mooncord.log
touch ~/printer_data/logs/mooncord.log # This creates a new empty file, skip if you don't use mooncord
sudo systemctl restart ratos-configurator
Yep that explains it left a dead symlink
c00ki3 vc4 300 IDEX
I will Report when I am at Home The fix will Remove it?
miklschmidt
miklschmidt2w ago
it would remove it and create a new empty file in it's place (which you probably don't need if you've uninstalled it)
c00ki3 vc4 300 IDEX
Ok, I unterstand I created the file and now it works. Maybe I have done anything wrong in uninstalling mooncord. Thanks a lot.
miklschmidt
miklschmidt2w ago
Probably. I'm not sure why it affected the configurator, that's very strange, but i haven't looked at mooncord at all. Maybe i should.
rm -rf "$MCLOGPATH/mooncord.log" > /dev/null
mkdir "/tmp/$MCSERVICENAME_ESC/"
touch "/tmp/$MCSERVICENAME_ESC/mooncord.log"
ln -s "/tmp/$MCSERVICENAME_ESC/mooncord.log" "$MCLOGPATH/mooncord.log"
rm -rf "$MCLOGPATH/mooncord.log" > /dev/null
mkdir "/tmp/$MCSERVICENAME_ESC/"
touch "/tmp/$MCSERVICENAME_ESC/mooncord.log"
ln -s "/tmp/$MCSERVICENAME_ESC/mooncord.log" "$MCLOGPATH/mooncord.log"
Well this is trouble. Explains why it stopped working when you attempted to uninstall it. There'll be a broken symlink as soon as your pi is restarted. Sort of an odd way to do logrollover.. but i guess it works everywhere lol
Want results from more Discord servers?
Add your server