Please check, as root, "whereis java" <- This command should tell you where your java executable is. But nevermind, since you already reinstalled, it's not an issue. Shit luck :) You could have replaced the password hash in the database directly, but I'm not sure which hashing scheme is used. But that will take another (couple of?) day(s?). So that will leave only the option to start an init script I gues. Therefore I started the tracker-server.jar file manually by means of the (self installed) java launcher.Īnd the "sudo systemctl enable traccar" does not work either to start automatically at reboot. The "sudo systemctl start traccar" command does not work. How come? Is it because I closed the Terminal while it was still systemctl is-active traccar Some remarkable issues: the traccar system remains in the "actvating" mode. I have no experience (yet) with init scripts or the use of systemd therefore I studied the sysytemctl commands today. I am happy that all steps I made before are now understandable to me and especially repeatable. Therefore I installed java with the following command:Īfter this I could install the traccar server again by means sudo java -jar /opt/traccar/tracker-server.jar /opt/traccar/conf/traccar.xml Therefore I installed Linux Desktop Ubuntu 20.10 again.Īfter the usual instructions, the outcome was that in the correct folder (/opt/traccar/jre/bin) the java command was not found. (The system kept remembering me with the wrong password). After login in with admin, admin, I made a typing error in the password and logged out.Īfter various trials, I decided to install the traccar server again. I was also able to restart the server (manually) after a restart of my Raspberry.Īfter that I made a "big mistake". This morning the system was still running.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |