- #Serviio console not starting how to
- #Serviio console not starting mac os x
- #Serviio console not starting update
- #Serviio console not starting driver
- #Serviio console not starting pro
My solution at the time, and this is still the situation, was to "just" build serviio-2.0.rpm and leave it sitting in the contribs-testing repo (from which no one should do automatic installations from).
#Serviio console not starting pro
IF I would have requested the ClearOS team to put the new serviio 2.0 package in the normal contribs repo (and subsequently contribs-verified later on), that would have forced anyone with a Pro licence on a ClearOS platform to having to buy a new license even if they were happy to stay where they were. I did what I normally do: packaged the new serviio-2.0.rpm but faced a problem that is a bit problematic: The way ClearOS is setup (for most users) is that there will be automatic updates whenever a newer package is available in the ClearOS repos, and there is "no way back". With it came also the requirement to buy a new Pro license as the old from "1.x" is not valid for "2.x". Now, a bit more than a year ago, upstream decided to go for a Serviio 2.0 release. I do however, package it into a serviio.rpm package for ClearOS whenever upstream releases a new version. The serviio program itself, and its roadmap is entirely done upstream. The Serviio Pro license is connected to Serviio, not to app-serviio. The app-serviio version number is NOT the same as the version number of the actual serviio program.
#Serviio console not starting update
For the last few releases Serviio has not changed its behaviour so there has not been any reason for me to make any update of app-serviio. It is called "app-serviio" and I update it if/when Serviio (or ClearOS) changes so installations and controlling (enable/disable the serviio service from the ClearOS webconfig page) is still possible. I develop/maintain the "wrapper" that installs Serviio using the ClearOS marketplace. But to maybe better understand how things work I will try to describe below a bit more detailed than you asked for. Not sure if I am the right guy to try to answer your question(s).
#Serviio console not starting driver
SQLException : No suitable driver found for jdbc : derby : db create = true at java. Is this a known issue? Can I help providing more information?Ģ013 - 01 - 20 22 : 25 : 05, 450 DEBUG Listening for application instances on socket 44331 2013 - 01 - 20 22 : 25 : 05, 462 INFO - 2013 - 01 - 20 22 : 25 : 05, 462 INFO Serviio DLNA media streaming server v 1.1 ( rev.
#Serviio console not starting how to
I don't know how to extract more debug information. I really don't know what's going on or if I'm doing something wrong. GateKeeper is set to allow applications downloaded from anywhere. I does the same and it doesn't output any error or warning. If I start the Serviio.app from the console with:
#Serviio console not starting mac os x
I've tried with the Console application in Mac OS X and I haven't found any error either. There is no error logged in /var/log/system.log The Serviio process is created when I start the app and then it just disappears a few seconds later. I've tried to trace the process with the Process Monitor. If I then start Serviio-Console.app, it opens a pop up saying "Cannot connect to Serviio server, it does not seem to be running. I then start Serviio.app, which starts bouncing in the Dock and dies mysteriously without opening any window, a few seconds after that. I download, unpack it and move Serviio.app and Serviio-Console.app to /Applications Java HotSpot (TM ) 64-Bit Server VM (build 20.12-b01-434, mixed mode )
0 kommentar(er)
