Hello
/var/log/syslog is getting 100MB every few minutes of these lines:
Nov 8 20:37:01 edi start-openas2.sh[182]: java.lang.NullPointerException
Nov 8 20:37:01 edi start-openas2.sh[182]: Nov 08, 2022 8:37:00 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 8 20:37:01 edi start-openas2.sh[182]: SEVERE: null
Nov 8 20:37:01 edi start-openas2.sh[182]: java.lang.NullPointerException
Nov 8 20:37:01 edi start-openas2.sh[182]: Nov 08, 2022 8:37:00 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 8 20:37:01 edi start-openas2.sh[182]: SEVERE: null
Nov 8 20:37:01 edi start-openas2.sh[182]: java.lang.NullPointerException
Nov 8 20:37:01 edi start-openas2.sh[182]: Nov 08, 2022 8:37:00 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 8 20:37:01 edi start-openas2.sh[182]: SEVERE: null
Nov 8 20:37:01 edi start-openas2.sh[182]: java.lang.NullPointerException
Nov 8 20:37:01 edi start-openas2.sh[182]: Nov 08, 2022 8:37:00 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 8 20:37:01 edi start-openas2.sh[182]: SEVERE: null
You need to start the application directly using the start_openas2.sh file from the command line.
That will show you what the real errors are that are causing the daemon launch to fail.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
# systemctl status openas2.service●openas2.service-OpenAS2ServerLoaded:loaded(/etc/systemd/system/openas2.service;enabled;vendorpreset:enabled)Active:active(running)sinceWed2022-11-0906:24:47EST;23sagoProcess:7813ExecStart=/opt/OpenAS2/bin/start-openas2.sh(code=exited,status=0/SUCCESS)MainPID:7826(java)Tasks:21(limit:309027)Memory:214.6MCPU:9.892sCGroup:/system.slice/openas2.service└─7826/usr/lib/jvm/java-8-oracle/jre/bin/java-Xms32m-Xmx384m-Dorg.apache.commons.logging.Log=org.openas2.logging.Log-Dopenas2.config.file=/opt/OpenAS2/bin/../config/confi>Nov0906:24:50edistart-openas2.sh[7826]:atjava.lang.Thread.run(Thread.java:748)Nov0906:24:50edistart-openas2.sh[7826]:Nov09,20226:24:49AMorg.openas2.cmd.processor.BaseCommandProcessor$1callNov0906:24:50edistart-openas2.sh[7826]:SEVERE:nullNov0906:24:50edistart-openas2.sh[7826]:java.lang.NullPointerExceptionNov0906:24:50edistart-openas2.sh[7826]:atorg.openas2.cmd.processor.StreamCommandProcessor.readLine(StreamCommandProcessor.java:107)Nov0906:24:50edistart-openas2.sh[7826]:atorg.openas2.cmd.processor.StreamCommandProcessor.processCommand(StreamCommandProcessor.java:49)Nov0906:24:50edistart-openas2.sh[7826]:atorg.openas2.cmd.processor.BaseCommandProcessor$1.call(BaseCommandProcessor.java:95)Nov0906:24:50edistart-openas2.sh[7826]:atorg.openas2.cmd.processor.BaseCommandProcessor$1.call(BaseCommandProcessor.java:90)Nov0906:24:50edistart-openas2.sh[7826]:atjava.util.concurrent.FutureTask.run(FutureTask.java:266)Nov0906:24:50edistart-openas2.sh[7826]:atjava.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
We have used systemd for a couple years to start openas2 .
I could try to use something besides systemd , however it may make sense to try to fix this issue for others .
I'll continue to work on this .
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It will not be solved using a different startup mechanism.
Fix your classpath and you will probably fix your systemd issue.
Starting from the command line is slightly different than launching using systemd in as much as the working directory will be different and the order of loading the jars will likely change so the use of old and new jars is not guaranteed to be in the same sequence meaning you will get random errors.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The start-openas2.sh file sets it.
Search for "CLASSPATH" in that file.
HOWEVER: In the log message for duplicate manifest files I see this:
Duplicate manifests detected: file:/opt/OpenAS2/lib/openas2-server-3.4.0.jar!/META-INF/MANIFEST.MF ::: file:/opt/OpenAS2/lib/openas2-server.jar!/META-INF/MANIFEST.MF
ie. Two different OpenAS2 server jar files in the same lib folder.
Since they re in the same folder, I am guessing you left all the old jars there and added the new ones which is going to create completely random results because the clas loader is not guranteed to load files in the same order every time you start a Java program.
I suggest you delete all files from the lib folder and copy all the files from the new package into the lib folder you are using for starting OpenAS2 (/opt/OpenAS2/lib)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
# Expand the classpath instead of using file globbing expansion in the java command as it seems to mess with Mailcap loadingCLASSPATH=$(echo"${binDir}/../lib/"*".jar"|tr' '':')# Include the bin dir so that commons-logging.properties is always foundCLASSPATH=${CLASSPATH}:${binDir}
I do this every upgrade so the the script does not need to be modified:
cd /opt/OpenAS2/lib
cp openas2-server-3.4.0.jar openas2-server.jar
that would cause two identical jar files at /opt/OpenAS2/lib
I'll try moving openas2-server-3.4.0.jar aside.
[ the rest of the jar files at /opt/OpenAs2/lib have the timestamp of Oct 3 13:37 ]
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am pretty certain you have mixed the 2.11 scripts and config with the 3.4.0 scripts and config.
The start-openas2.sh for 3.4.0 appends the bin folder to the classpath but your log shows it prepended which means you are starting it with the old script.
Can you upload an obfuscated version of your config.xml and partnerships.xml
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you provide the output from this command (assuming the systemd service is called "openas2"): journalctl -u openas2.service
Also, please check if the error in the syslog occurs at very set intervals as that may narrow join the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the output from journalctl is over 100MB. using less the entire output seems to be the following:
-- Journal begins at Tue 2022-11-08 20:30:52 EST, ends at Wed 2022-11-09 14:15:31 EST. --
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
I'll upload the config files next.
I did notice some %home% in config.xml . th database upgrade procedure failed until I change %home% s to fll pathname .
the output from journalctl is over 100MB. using less the entire output seems to be the following:
-- Journal begins at Tue 2022-11-08 20:30:52 EST, ends at Wed 2022-11-09 14:15:31 EST. --
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
Nov 08 20:30:52 edi start-openas2.sh[2093]: java.lang.NullPointerException
Nov 08 20:30:52 edi start-openas2.sh[2093]: Nov 08, 2022 8:30:51 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 08 20:30:52 edi start-openas2.sh[2093]: SEVERE: null
I'll upload the config files next.
I did notice some %home% in config.xml . th database upgrade procedure failed until I change %home% s to fll pathname .
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
also regarding : 'Also, please check if the error in the syslog occurs at very set intervals as that may narrow join the problem.'
syslog gets well over 900MB of the same lines posted every 5 minutes.
these repeat:
`
Nov 9 14:22:46 edi start-openas2.sh[39524]: Nov 09, 2022 2:22:46 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 9 14:22:46 edi start-openas2.sh[39524]: SEVERE: null
Nov 9 14:22:46 edi start-openas2.sh[39524]: java.lang.NullPointerException
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.StreamCommandProcessor.readLine(StreamCommandProcessor.java:107)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.StreamCommandProcessor.processCommand(StreamCommandProcessor.java:4>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.BaseCommandProcessor$1.call(BaseCommandProcessor.java:95)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.BaseCommandProcessor$1.call(BaseCommandProcessor.java:90)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.FutureTask.run(FutureTask.java:266)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThre>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolE>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.lang.Thread.run(Thread.java:748)
Nov 9 14:22:46 edi start-openas2.sh[39524]: Nov 09, 2022 2:22:46 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 9 14:22:46 edi start-openas2.sh[39524]: SEVERE: null
Nov 9 14:22:46 edi start-openas2.sh[39524]: java.lang.NullPointerException
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.StreamCommandProcessor.readLine(StreamCommandProcessor.java:107)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.StreamCommandProcessor.processCommand(StreamCommandProcessor.java:4>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.BaseCommandProcessor$1.call(BaseCommandProcessor.java:95)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.BaseCommandProcessor$1.call(BaseCommandProcessor.java:90)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.FutureTask.run(FutureTask.java:266)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThre>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolE>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.lang.Thread.run(Thread.java:748)
`
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I spent a couple of hours doing a fresh upgrade . this time I followed the appendix and tried this upgrade method :
using the existing /opt/OpenAs2/ , rm existing lib directory and copying over new etc. also copied over the new config/DB/openas2.mv.db
after that the logs are filling up as before.
I wanted to try a fresh upgrade to make certain things like the lib directory were as they should be.
In a few hours I will get back to this and start by checking my config.xml and partnerships.xml for something that may be causing the issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
re: Set this to "false" in the config.xml:
console.command.processor.enabled="true"
that did not fix. syslog listing:
root@edi:[/var/log]:# ls -lh syslog ;date-rw-r-----1rootadm143MNov1007:06syslogThuNov1007:06:57EST2022root@edi:[/var/log]:# ls -lh syslog ;date-rw-r-----1rootadm162MNov1007:07syslogThuNov1007:07:00EST2022root@edi:[/var/log]:# ls -lh syslog ;date-rw-r-----1rootadm181MNov1007:07syslogThuNov1007:07:04EST2022root@edi:[/var/log]:# ls -lh syslog ;date-rw-r-----1rootadm221MNov1007:07syslogThuNov1007:07:10EST2022root@edi:[/var/log]:# systemctl stop openas2.serviceroot@edi:[/var/log]:# ls -lh syslog ;date-rw-r-----1rootadm268MNov1007:07syslogThuNov1007:07:21EST2022root@edi:[/var/log]:# ls -lh syslog ;date-rw-r-----1rootadm268MNov1007:07syslogThuNov1007:07:28EST2022
Also - I am running edi in a lxc container . Perhaps a KVM would do better?
Last edit: robfantini2 2022-11-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
/var/log/syslog is getting 100MB every few minutes of these lines:
Nov 8 20:37:01 edi start-openas2.sh[182]: java.lang.NullPointerException Nov 8 20:37:01 edi start-openas2.sh[182]: Nov 08, 2022 8:37:00 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call Nov 8 20:37:01 edi start-openas2.sh[182]: SEVERE: null Nov 8 20:37:01 edi start-openas2.sh[182]: java.lang.NullPointerException Nov 8 20:37:01 edi start-openas2.sh[182]: Nov 08, 2022 8:37:00 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call Nov 8 20:37:01 edi start-openas2.sh[182]: SEVERE: null Nov 8 20:37:01 edi start-openas2.sh[182]: java.lang.NullPointerException Nov 8 20:37:01 edi start-openas2.sh[182]: Nov 08, 2022 8:37:00 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call Nov 8 20:37:01 edi start-openas2.sh[182]: SEVERE: null Nov 8 20:37:01 edi start-openas2.sh[182]: java.lang.NullPointerException Nov 8 20:37:01 edi start-openas2.sh[182]: Nov 08, 2022 8:37:00 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call Nov 8 20:37:01 edi start-openas2.sh[182]: SEVERE: null
An idea what can be done to solve this issue?
I search the forum and found this:
https://sourceforge.net/p/openas2/discussion/265567/thread/ad254a4865/?limit=25#0921
however did not see a sentdir line to change.
besides the log error I was able to send a file and received a AsyncMDN
I changed the config files to new format.
the errors continue
/var/log/syslog are getting close to 100MB larger every minute.
You need to start the application directly using the start_openas2.sh file from the command line.
That will show you what the real errors are that are causing the daemon launch to fail.
Hello,
starting from cli, here is the output:
the startup looks okay to me,
the logs are quiet .
and was able to send a test file and get a MDN .
I'll test stopping the service and start it using systemd
Lookss like you have old and new jars mixed together.
Look at tthis:
It may be the CLASSPATH setting for the java command (the "-cp" bit) including the old and new jars.
I am unfamiliar with java.
would these jars be located within openas2 directories ? Or part of java software ?
start using systemd causes the issue.
We have used systemd for a couple years to start openas2 .
I could try to use something besides systemd , however it may make sense to try to fix this issue for others .
I'll continue to work on this .
It will not be solved using a different startup mechanism.
Fix your classpath and you will probably fix your systemd issue.
Starting from the command line is slightly different than launching using systemd in as much as the working directory will be different and the order of loading the jars will likely change so the use of old and new jars is not guaranteed to be in the same sequence meaning you will get random errors.
forgive my lack of java knowledge...
Is classpath configured in a openas2 file or operating system?
The start-openas2.sh file sets it.
Search for "CLASSPATH" in that file.
HOWEVER: In the log message for duplicate manifest files I see this:
Duplicate manifests detected: file:/opt/OpenAS2/lib/openas2-server-3.4.0.jar!/META-INF/MANIFEST.MF ::: file:/opt/OpenAS2/lib/openas2-server.jar!/META-INF/MANIFEST.MF
ie. Two different OpenAS2 server jar files in the same lib folder.
Since they re in the same folder, I am guessing you left all the old jars there and added the new ones which is going to create completely random results because the clas loader is not guranteed to load files in the same order every time you start a Java program.
I suggest you delete all files from the lib folder and copy all the files from the new package into the lib folder you are using for starting OpenAS2 (/opt/OpenAS2/lib)
from start-openas2.sh:
I do this every upgrade so the the script does not need to be modified:
cd /opt/OpenAS2/lib
cp openas2-server-3.4.0.jar openas2-server.jar
that would cause two identical jar files at /opt/OpenAS2/lib
I'll try moving openas2-server-3.4.0.jar aside.
[ the rest of the jar files at /opt/OpenAs2/lib have the timestamp of Oct 3 13:37 ]
after moving the extra jar file the startup error seems to be gone:
logs are quiet
classpath looks okay to me ...
from what you see above let me know if that solved the classpath issue.
after moving the extra jar file the startup error seems to be gone:
logs are quiet
classpath looks okay to me ...
from what you see above let me know if that solved the classpath issue.
assuming the claspath is fixed, I tested starting with systemd, and the logs are filling up at 100MB per minute.
here is the systemd config :
that config has worked since 2017 .
let me know if you spot something that could be tried to fix the systemd config.
PS:
I greatly appreciate your help.... will be back in a few hours.
next tried using /opt/OpenAS2/bin/openas2.service which was slightly different .
that did not solve the issue.
I am pretty certain you have mixed the 2.11 scripts and config with the 3.4.0 scripts and config.
The start-openas2.sh for 3.4.0 appends the bin folder to the classpath but your log shows it prepended which means you are starting it with the old script.
Can you upload an obfuscated version of your config.xml and partnerships.xml
Can you provide the output from this command (assuming the systemd service is called "openas2"):
journalctl -u openas2.service
Also, please check if the error in the syslog occurs at very set intervals as that may narrow join the problem.
the output from journalctl is over 100MB. using less the entire output seems to be the following:
I'll upload the config files next.
I did notice some %home% in config.xml . th database upgrade procedure failed until I change %home% s to fll pathname .
the output from journalctl is over 100MB. using less the entire output seems to be the following:
I'll upload the config files next.
I did notice some %home% in config.xml . th database upgrade procedure failed until I change %home% s to fll pathname .
also regarding : 'Also, please check if the error in the syslog occurs at very set intervals as that may narrow join the problem.'
syslog gets well over 900MB of the same lines posted every 5 minutes.
these repeat:
`
Nov 9 14:22:46 edi start-openas2.sh[39524]: Nov 09, 2022 2:22:46 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 9 14:22:46 edi start-openas2.sh[39524]: SEVERE: null
Nov 9 14:22:46 edi start-openas2.sh[39524]: java.lang.NullPointerException
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.StreamCommandProcessor.readLine(StreamCommandProcessor.java:107)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.StreamCommandProcessor.processCommand(StreamCommandProcessor.java:4>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.BaseCommandProcessor$1.call(BaseCommandProcessor.java:95)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.BaseCommandProcessor$1.call(BaseCommandProcessor.java:90)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.FutureTask.run(FutureTask.java:266)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThre>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolE>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.lang.Thread.run(Thread.java:748)
Nov 9 14:22:46 edi start-openas2.sh[39524]: Nov 09, 2022 2:22:46 PM org.openas2.cmd.processor.BaseCommandProcessor$1 call
Nov 9 14:22:46 edi start-openas2.sh[39524]: SEVERE: null
Nov 9 14:22:46 edi start-openas2.sh[39524]: java.lang.NullPointerException
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.StreamCommandProcessor.readLine(StreamCommandProcessor.java:107)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.StreamCommandProcessor.processCommand(StreamCommandProcessor.java:4>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.BaseCommandProcessor$1.call(BaseCommandProcessor.java:95)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at org.openas2.cmd.processor.BaseCommandProcessor$1.call(BaseCommandProcessor.java:90)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.FutureTask.run(FutureTask.java:266)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThre>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolE>
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Nov 9 14:22:46 edi start-openas2.sh[39524]: #011at java.lang.Thread.run(Thread.java:748)
`
I spent a couple of hours doing a fresh upgrade . this time I followed the appendix and tried this upgrade method :
using the existing /opt/OpenAs2/ , rm existing lib directory and copying over new etc. also copied over the new config/DB/openas2.mv.db
after that the logs are filling up as before.
I wanted to try a fresh upgrade to make certain things like the lib directory were as they should be.
In a few hours I will get back to this and start by checking my config.xml and partnerships.xml for something that may be causing the issue.
Looks like it might be the stream command processor.
Set this to "false" in the config.xml:
console.command.processor.enabled="true"
... and restart.
to give you a better idea on log issue,
I have logs set to rotate 5x hour.
here are some of the sizes . and note root disk close to full:
Probably there is something unusual with our configuration as others have not seen this issue.
I am sure we will get this fixed.
re: Set this to "false" in the config.xml:
console.command.processor.enabled="true"
that did not fix. syslog listing:
Also - I am running edi in a lxc container . Perhaps a KVM would do better?
Last edit: robfantini2 2022-11-10