For development I'm starting OM like this JAVA_OPTS="-DDATA_DIR=/home/solomax/work/openmeetings/data" ./bin/catalina.sh jpda run
for openmeetings.service start script you can have Environment='JAVA_OPTS=-Djava.awt.headless=true -DDATA_DIR=/opt/omdata5' On Mon, 28 Sep 2020 at 16:53, Ali Alhaidary <[email protected]> wrote: > And of course, > > 5. chown ..... > On 9/28/20 12:51 PM, Ali Alhaidary wrote: > > So many thanks, this would be really so good. Can I do the following: > > 1. stop OM > 2. mv om_folder to om_folder.bak > 3. unpack new snapshot to om_folder > 4. cp > /opt/om_foldr.bak/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml > to > > /opt/om_floder/webapps/openmeetings/WEB-INF/classes/META-INF/persistence.xml > 5. cp /opt/om_folder.bak/conf/server.xml to > /opt/om_folder/conf/server.xmlalong with the certificate > > But, how to set the same DATA_DIR and where? > > > On 9/28/20 4:51 AM, Maxim Solodovnik wrote: > > You can > 1) unpack new snapshot to NEW location > 2) set the same DATA_DIR > 3) copy your old persistence.xml > 3.1***) some other configs might need to be copied > 4) start new instance > > and everything should work as before :) > > On Sun, 27 Sep 2020 at 12:16, Ali Alhaidary <[email protected]> > wrote: > >> Clarification: >> >> If we replace these files from a downloaded and unzipped #68 snapshot >> (the html files with the same name) ? >> >> >> On 9/27/20 7:57 AM, Ali Alhaidary wrote: >> >> Hi, >> >> we are now running snapshot #67, is it OK if we replace only these 4 >> files: >> >> FileItem.java >> TestExport.java >> Recording.java >> BackupExport.java >> >> And we will be on snapshot #68 ? >> On 9/27/20 5:37 AM, Maxim Solodovnik wrote: >> >> https://issues.apache.org/jira/browse/OPENMEETINGS-2459 >> >> please do not use backup/restore for now >> just re-use previous DB >> >> On Sun, 27 Sep 2020 at 07:24, Maxim Solodovnik <[email protected]> >> wrote: >> >>> these can be ignored >>> >>> others: >>> [39mDEBUG [0;39m 09-26 10:30:39.827 [36mo.a.o.b.BackupExport:407 [main] >>> [0;39m - Exception While writing node of type: class >>> org.apache.openmeetings.db.entity.file.FileItem >>> javax.xml.bind.MarshalException: null >>> >>> at >>> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:301) >>> at >>> com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:226) >>> at >>> javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:101) >>> at >>> org.apache.openmeetings.backup.BackupExport.writeList(BackupExport.java:404) >>> at >>> org.apache.openmeetings.backup.BackupExport.stream(BackupExport.java:374) >>> at >>> org.apache.openmeetings.backup.BackupExport.writeList(BackupExport.java:381) >>> at >>> org.apache.openmeetings.backup.BackupExport.exportFile(BackupExport.java:337) >>> at >>> org.apache.openmeetings.backup.BackupExport.performExport(BackupExport.java:188) >>> at org.apache.openmeetings.cli.Admin.processBackup(Admin.java:365) >>> at org.apache.openmeetings.cli.Admin.process(Admin.java:263) >>> at org.apache.openmeetings.cli.Admin.main(Admin.java:563) >>> >>> Caused by: com.sun.istack.SAXException2: >>> com.sun.xml.bind.api.AccessorException: The property has a setter "public >>> void org.apache.openmeetings.db.entity.file.FileItem.setId(java.lang.Long)" >>> but no getter. For marshaller, please define getters. >>> >>> at >>> com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:217) >>> at >>> com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:232) >>> at >>> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:340) >>> at >>> com.sun.xml.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:563) >>> at >>> com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:311) >>> at >>> com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:464) >>> at >>> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:298) >>> ... 10 common frames omitted >>> >>> >>> can't be ignored >>> I'm going to investigate it ASAP >>> this might be blocker >>> >>> >>> On Sat, 26 Sep 2020 at 17:39, Ali Alhaidary <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> Trying to do back up by command line OM 5.0.1 old snapshot, I got on >>>> screen these lines and attached a file for the output >>>> >>>> Sep 26, 2020 10:30:34 AM >>>> com.hazelcast.internal.config.AbstractConfigLocator >>>> INFO: Loading 'hazelcast.xml' from the classpath. >>>> Sep 26, 2020 10:30:34 AM >>>> com.hazelcast.instance.impl.HazelcastInstanceFactory >>>> WARNING: Hazelcast is starting in a Java modular environment (Java 9 >>>> and >>>> newer) but without proper access to required Java packages. Use >>>> additional Java arguments to provide Hazelcast access to Java internal >>>> API. The internal API access is used to get the best performance >>>> results. Arguments to be used: >>>> --add-modules java.se --add-exports >>>> java.base/jdk.internal.ref=ALL-UNNAMED --add-opens >>>> java.base/java.lang=ALL-UNNAMED --add-opens >>>> java.base/java.nio=ALL-UNNAMED --add-opens >>>> java.base/sun.nio.ch=ALL-UNNAMED --add-opens >>>> java.management/sun.management=ALL-UNNAMED --add-opens >>>> jdk.management/com.sun.management.internal=ALL-UNNAMED >>>> WARNING: An illegal reflective access operation has occurred >>>> WARNING: Illegal reflective access by >>>> com.hazelcast.internal.networking.nio.SelectorOptimizer >>>> (file:/opt/open500/webapps/openmeetings/WEB-INF/lib/hazelcast-4.0.2.jar) >>>> >>>> to field sun.nio.ch.SelectorImpl.selectedKeys >>>> WARNING: Please consider reporting this to the maintainers of >>>> com.hazelcast.internal.networking.nio.SelectorOptimizer >>>> WARNING: Use --illegal-access=warn to enable warnings of further >>>> illegal >>>> reflective access operations >>>> WARNING: All illegal access operations will be denied in a future >>>> release >>>> >>>> My question is: should I just ignore them and move on ? >>>> >>>> >>> >>> -- >>> Best regards, >>> Maxim >>> >> >> >> -- >> Best regards, >> Maxim >> >> > > -- > Best regards, > Maxim > > -- Best regards, Maxim
