Ebase doesn't log fatal errors any more

Post any questions you have about using the Verj.io Studio, including client and server-side programming with Javascript or FPL, and integration with databases, web services etc.

Moderators: Jon, Steve, Ian, Dave

Segi
Ebase User
Posts: 649
Joined: Mon Dec 09, 2013 6:37 pm

Ebase doesn't log fatal errors any more

#1

Postby Segi » Thu Aug 10, 2017 5:51 pm

I have noticed that Ebase doesn't write fatal errors (server side errors and form.abort messages) to the log any more.

If I do print("This is a log message"); the message is added to the log.

A few months ago, I was debugging a problem with PDF documents not rendering correctly and added an entry to log4j (http://forum.ebasetech.com/forum/viewto ... highlight=) which I believe that I undid correctly. In any case, here is my log4j.xml: https://pastebin.com/MthPWpCE

(I can't post the file contents here because the forum software tries to render the XML as HTML code even inside code blocks)

I compared this log4j to the one from my other Ebase instance and they look the same.

I mention log4j because thats the only related thing that I can thing of that would cause this but I'm not 100% sure that its the source of the problem
0 x

Segi
Ebase User
Posts: 649
Joined: Mon Dec 09, 2013 6:37 pm

#2

Postby Segi » Thu Aug 31, 2017 3:47 pm

Anyone know what could be causing this ? It's making it very difficult to trouble shoot errors.
0 x

Jon
Moderator
Moderator
Posts: 1342
Joined: Wed Sep 12, 2007 12:49 pm

#3

Postby Jon » Fri Sep 01, 2017 6:32 am

Your log4j.xml looks OK. I suggest you check the logInfo and logError settings in the server.properties file in ebaseConf. You can see this using the Server Admin > Properties.
0 x


Who is online

Users browsing this forum: No registered users and 6 guests