WesGilster
commented
7 years ago This is definitely due to Javascript going a bit wild in your custom version. The logs are showing some serious spamming of the "http://localhost:9091/services/printJobs/getByPrinterName/" method. Perhaps the Javascript has gotten caught in some refresh loop of some sort?
Thanks, Wes G. On 11/16/2016 12:02 PM, Robin wrote:
Hi,
I just had the following error on an clean install, it might be due our costum version so I asked WG as well. But it looks like a photonic error. What happens is that I just installed the profile from github (which we used before) but when I started the printer I got the error "internal server error" and wouldn't start when I took a look at the printer configuration I couldn't pick a single display device.
LogBundle (6).zip https://github.com/area515/Photonic3D/files/595494/LogBundle.6.zip
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/area515/Photonic3D/issues/287, or mute the thread https://github.com/notifications/unsubscribe-auth/ACT_NNKWx3cvC1KUsHCXQIh_yA5TS6R9ks5q-0VTgaJpZM4K0O2j.
kloknibor
Hi,
I just had the following error on an clean install, it might be due our costum version so I asked WG as well. But it looks like a photonic error. What happens is that I just installed the profile from github (which we used before) but when I started the printer I got the error "internal server error" and wouldn't start when I took a look at the printer configuration I couldn't pick a single display device.
LogBundle (6).zip