Open eshenayo opened 10 months ago
What were you trying to do when running the devicestarter.sh
? Were you trying to run Possum locally? If so, there are steps detailed in the ReadMe to assist with this process here. We are trying to make our ReadMe more detailed, so if these steps are unclear, please reach out and we will try to update them accordingly.
Usually when running locally, we don't run the devicestarter.sh
because it is meant to be used on a physical register with devices attached. As detailed in our Sequence Overview Diagram the devicestarter.sh
defines classpaths and libraries and then starts Possum. When running locally, we bypass this setup step by starting Possum with gradle instead of the script. Hope this helps!
Thanks for the reply! Yes, I was trying to run the script locally, but it is being run on a physical register with the devices attached.
Do you have a register that you are running devicestarter.sh
on that is not working? Were you able to get Possum up and running on your local machine?
I have possum running, but it isn't picking up any of the attached devices:
023-11-07T09:50:57.269-07:00 INFO 151066 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
2023-11-07T09:50:57.551-07:00 INFO 151066 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 2152 ms
2023-11-07T09:50:57.792-07:00 DEBUG 151066 --- [ main] c.t.d.configuration.ApplicationConfig : Application Version - PACKAGE_VERSION
2023-11-07T09:50:57.793-07:00 DEBUG 151066 --- [ main] c.t.d.configuration.ApplicationConfig : Is Simulation Mode - false
jpos/res/jpos.properties file not found
jpos/res/jpos.properties file not found
jpos/res/jpos.properties file not found
2023-11-07T09:50:58.657-07:00 INFO 151066 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 3 endpoint(s) beneath base path ''
2023-11-07T09:50:58.773-07:00 INFO 151066 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ''
2023-11-07T09:50:58.800-07:00 INFO 151066 --- [ main] com.target.devicemanager.DeviceMain : Started DeviceMain in 4.108 seconds (process running for 4.489)
2023-11-07T09:50:58.865-07:00 DEBUG 151066 --- [ main] com.target.devicemanager.DeviceMain : Setting default log path for POSSUM.
2023-11-07T09:51:04.880-07:00 INFO 151066 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet'
2023-11-07T09:51:04.883-07:00 INFO 151066 --- [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 3 ms
2023-11-07T09:51:04.939-07:00 ERROR 151066 --- [nio-8080-exec-1] c.t.d.common.DeviceAvailabilityService : JSON is in wrong format
2023-11-07T09:51:07.291-07:00 ERROR 151066 --- [nio-8080-exec-2] c.t.d.common.DeviceAvailabilityService : JSON is in wrong format
And when hitting the peripherals endpoint, there is an error in the output of the possum run that the format is incorrect
When you run the simulator, are you using the command ./gradlew run -DuseSimulators=true
?
I'm not running the simulator, I have peripherals that I want to verify control of. I have the env variable set to local
for SPRING_PROFILES_ACTIVE
I am running the command as:
cd $POSSUM_DIR
sudo -E ./gradlew run
Where POSSUM_DIR is set to the cloned repository base. I already ran sudo -E ./gradlew build
and I have the drivers for my peripherals installed (NCR, HP and Zebra)
When running
sudo ./devicestarter.sh
I get the error:Which is from this line:
This may be user error.