I'm trying out a new cloud-based server running Debian 10-x86_64-ge. Jamulus compile (3.5.9git) went fine however I'm getting this error when attempting to launch the service.
So I removed the --history argument and the service runs fine now.
Why would the --history option not work in this case? I've used the exact same compile and launch steps on another cloud-based service running Debian 10 with no problems.
Any help is greatly appreciated.
Last edit: Al Udell 2020-08-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
History is now part of this set of useful tools from the Jamulus repository (clone the Git repo and also call git submodule update --init to get them).
Okay, thanks. So I'm reading that to use the new history tool, you need to run a webserver (including PHP) that has access to the server-side location of the Jamulus log. This adds another layer of complexity to a Jamulus install but I understand that it was needed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm trying out a new cloud-based server running Debian 10-x86_64-ge. Jamulus compile (3.5.9git) went fine however I'm getting this error when attempting to launch the service.
So I removed the --history argument and the service runs fine now.
Why would the --history option not work in this case? I've used the exact same compile and launch steps on another cloud-based service running Debian 10 with no problems.
Any help is greatly appreciated.
Last edit: Al Udell 2020-08-12
The history file is no longer generated inside the Jamulus software but is generated by external tools now: https://github.com/corrados/jamulus/issues/501
Oh, okay, I did not know that --histdays and --history are now deprecated. How does one get the history feature working now?
Last edit: Al Udell 2020-08-12
History is now part of this set of useful tools from the Jamulus repository (clone the Git repo and also call
git submodule update --initto get them).https://github.com/corrados/jamulus/tree/master/tools
Okay, thanks. So I'm reading that to use the new history tool, you need to run a webserver (including PHP) that has access to the server-side location of the Jamulus log. This adds another layer of complexity to a Jamulus install but I understand that it was needed.
Oh, didn't realise you neeeded a web server. Seems like it depends on JQuery to render stuff in a browser.
Definitely need a webserver. The new history tool uses PHP and JS/JSON to serve the graph.