dtools | DICOM tools set Simple DICOM client | Messaging library

Found the issue. I had to change this line:

JVM Crashing for Grails 2.4.2 application while upgrading from Java 7 to Java 8

Grails 2.5 is the first version of Grails for which we support Java 8.

Your code actually works for PyTorch >= 0.4.1. I guess your PyTorch version is < 0.4 and so you need to pass a Variable in the following line.

I sometimes have the same problem. For whatever reason the first instance hasn't exited cleanly and is still listening on the addr/port combo of the mountpoint, preventing the new instance from binding to it. You can fix it without rebooting, you need to find the process causing the problem and then kill it.

For example let's say your mountpoint is listening on port 8800, you can use the lsof command to identify the old process. Add the -i option and specify the interface/port to return results for and you'll get something like this:

lsof -i:8800

OK, so Icecast itself seems to be running fine. (you can see it answering a simple request for '/' from localhost) If you don't see at least the very basic web interface, please check your firewall settings and browser. Consider adding :: and restarting Icecast (sudo systemctl restart icecast2.service or sudo /etc/init.d/icecast2 restart) for improved compatibility. (That will bind to IPv6 and legacy-IP aka IPv4. It's mostly cosmetic though.)

The EROR connection/_handle_connection HTTP request parsing failed is most likely unrelated to your problems. Possibly Liquidsoap or some other process doing something stupid, but not critical.

Make sure that Liquidsoap is using the password specified here: ******

Please also examine /home/username/liquidsoap-daemon/log/radioliq.log for further hints.

On Debian and its derivatives (Ubuntu, Mint, etc) Liquidsoap runs as the liquidsoap user. By default this user does not have write access to /home/username/liquidsoap-daemon/log/radioliq.log. Either that directory needs write access given to that user or one might elect to use /var/log/liquidsoap which is already set up appropriately.

If Liquidsoap can not start logging, then it will refuse to start. Just what seems to have happened here.

There may be other problems once that's corrected, please then refer to the log for details.

You are using the wrong variables, the following should work and is the highest supported by 4.9

Your classpath is expecting the wrapper jar to be in the wrapper/grails-wrapper-runtime-2.5.0.jar location relative to the directory in which you are running the command. Are you running the command in the project directory where the shell script can locate the wrapper runtime jar? If not, you will need to update the classpath in the script to point to the absolute path or use dirname command to evaluate the classpath directory.

I believe the problem could be the grails version you have 'grails-2.5.6'.

The jB CE 4.x version is based on grails-2.4.3. You should use that.