12 | Replication error on slave restart="50" user="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger name="*" level="info ... inactivity-timeout="0" /> <url-history size="50" user="true" password="true" /> <log path |
12 | Out of memory, heap size is set to 1536MB. Log files are empty. Database uptime was about 3 weeks. It's still version ... lot of data from other source). I didn't catch the size of record log file. For now I turned on heap ... screenshots. Record log is almost 50MB large. Database is about 73MB large. The strange thing |
12 | UserException: Invalid configuration in 'internal' - Check permissions is thrown because ObjectDB doesn't have a permission to create a log file in the default path (as ... ). See the manual for explanation on the log directory and ObjectDB Home, and either change permissions for the default log path, or change ObjectDB home, or change the log path by adding your own configuration file |
11 | Connection is closed Caused by: java.io.EOFException/ObjectDB" threshold="64mb" /> <network inactivity-timeout="0" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90 ... ! longpat Brian O'Hare Actually, I was concentrating so much on my own logs that I neglected the ObjectDB |
11 | Unexpected exception during open the database you for this clarification. Some more information may help. Are these exceptions written to the log? thrown ... except getting these exception in the log. You wrote: > do have an idea why we get following ... . Are these exceptions written to the log? thrown? stop anything? In this particular case, the access to the database |
11 | ObjectDB is opening too many sockets the whole process as this is a blocker for production use. thamal Tomas Hamal ODB Log prints ... _SOCKET, SO_LINGER, {l_onoff=0, l_linger=0}, [8]) = 0 Here is example of strace log during standard ... strace log as I wrote above. But I am under impression, that creating heap dump also triggers GC |
11 | ObjectDB shuts down, or some similar inactivity. When inspecting the log it doesn’t show anything why the database has stopped. DB can be normally started after it shutdowns and log continues. Logging is currently set to TRACE level. ObjectDB is running on CentOS, and it doesn’t show any problems, log doesn’t log any |
10 | virtual servers and one file which configuration file in actually used in the log. You may also insert a deliberate error in the objectdb ... -timeout="0" /> <url-history size="50" user="true" password="true" /> <log path="" max="8mb" stdout="false" stderr="false" /> <log-archive path="" retain="0" /> <logger name="*" level="info" /> </general |
2 | Negative snapshot user count exceptionI found the following stack trace in my log files; it's cropped up a number of times: [2013-08-23 ... prefix failure, and some other problems (see attached log file). Last week I had inadvertently left ... PDT (circa 9/10 @02:40 UTC). After restarting the database (see log entry [2013-09-10 02:44:10 #1 |
2 | each 1-2 days objects on some objectdb level lock/block each other="true" password="true" /> <log path="$objectdb/log/" max="8mb" stdout="false" stderr="false" /> <log-archive path="$objectdb/log/archive/" retain="90" /> <logger name ... that activity in your log files (or in ObjectDB log files if you enable logging queries |
