Describe the issue in full detail, including screenshots if possible:
I have just installed the latest version and uploaded my musicfiles an created a playlist.
After restarting the station the music files are not played,it keeps playing only the azurast demo file>
Also when editing the mountpoint i do get this error:
500
Call to a member function getId() on null
MountsController.php : 134
@surihost Regarding the MountsController issue, please don't put more than one request on a single Github issue.
Considering the MountsController issue (which already exists as #405) has recently been resolved, I'm not sure you're updated to the very latest version of the code. Can you run the update script again with the latest version, and verify that the issue still exists?
I have just updated, but the problem is still there.Autodj is not working.
I deleted the playlist,created again a new one,restarted but still the same.
Maybe some bug that when creating the paylist it doesnt take take or save the content of the songs?
I just updated, everything works the error was gone, I've had such a mistake before.
Yes the 500 error is gone,but the autodj still not working.
With this, I also agree at all it is not clear how it works, if you watch reports, then many songs, he does not lose at all from added ones. Why is it not clear how to make him lose all the songs for me is not clear. Perhaps the author will clarify the situation, I initially thought that it all depends on the rating of the songs.
Hope to see a fix for this,still the autodj not working.
Heh, reading this thread is like watching a contest where both sides are trying to figure out who can understand the other _less_.
@surihost Just telling me "thing isn't working" is not likely to lead to a quick or simple response. Rather than just going in and fixing the relevant error message, I have to type out a long string of diagnostic commands for you to try, then wait for you to try them, etc...if you pursued these diagnostics before submitting the original issue, things will go a lot faster.
In this case (as in many cases with Docker) your debugging process should be to run, inside the AzuraCast folder:
docker-compose logs -f stations
(If nginx is having trouble, replace "stations" with "nginx"...if it's the web app, replace it with "web", and so on...using the same names as the services in docker-compose.yml)
Try restarting the station and see if errors appear. If they do, paste them here.
Here the logs:
stations_1 | 2018/02/15 12:29:30 [radio_out_1:3] Will try again in 3.00 sec.
stations_1 | 2018-02-15 12:29:30 ERROR [SRC 127.0.0.1:47084 sid=1] SHOUTcast 1 source rejected. A source is already connected.
stations_1 | strange error flushing buffer ...
stations_1 | strange error flushing buffer ...
stations_1 | 2018/02/15 12:29:30 main.go:90: Change in content: triggering web hook
stations_1 | 2018/02/15 12:29:34 [radio_out_1:3] Connecting mount sid#1 for @127.0.0.1...
stations_1 | 2018/02/15 12:29:34 [radio_out_1:2] Connection failed: bad answer: Stream In Use
stations_1 | 2018/02/15 12:29:34 [radio_out_1:3] Will try again in 3.00 sec.
stations_1 | 2018-02-15 12:29:34 ERROR [SRC 127.0.0.1:47148 sid=1] SHOUTcast 1 source rejected. A source is already connected.
@surihost Do you have two stations trying to use the same port range? Up until fairly recently, cloning a station didn't properly assign it a new radio port, so you may need to make sure stations aren't trying to stack directly on top of each other port-wise.
No i dont have stations using the same port.
If i restream on the same station(port) it works and when i want use playlist to play the songs i have uploaded it doesnt work,only plays the azuracast demo.
@surihost Per the error, _something_ is getting between the Liquidsoap AutoDJ and the Shoutcast instance.
I'd start by verifying that there are no other radio sources connected to the same Shoutcast endpoint, and this includes running a command like:
docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)
to ensure all containers are stopped, then run the usual docker-compose up -d to spin the correct ones back up again.
I did as mentioned,still the autodj not working.
[root@ls azuracast]# docker stop $(docker ps -a -q)
e76b8ccb0e76
de12555213d9
d86f9b5a76ff
c8b407c8be5e
00889c0fa72c
a39aed257ce3
445438567dd2
a09599c25235
62d37844b2ca
[root@ls azuracast]# docker rm $(docker ps -a -q)
e76b8ccb0e76
de12555213d9
d86f9b5a76ff
c8b407c8be5e
00889c0fa72c
a39aed257ce3
445438567dd2
a09599c25235
62d37844b2ca
Creating azuracast_stations ... done
Creating azuracast_redis_1 ... done
Creating azuracast_influxdb_1 ... done
Creating azuracast_letsencrypt_1 ... done
Creating azuracast_cron ... done
Creating azuracast_stations ...
Creating azuracast_web_1 ... done
Creating azuracast_redis_1 ...
Creating azuracast_influxdb_1 ...
Creating azuracast_web_1 ...
Creating azuracast_nginx_1 ... done
Creating azuracast_cli_1 ...
Creating azuracast_cli_1 ... done
@surihost Unfortunately, after taking a look at your reported issue and being unable to reproduce it on my local installation, it seems the best way for me to diagnose this issue further would be to directly take a look at your AzuraCast instance. There may be something specific to your setup that we aren't testing for, or something could be misconfigured in the application.
If you're willing to have me take a direct look at your installation for easier and faster issue resolution, please send an e-mail to [email protected] with the details of a temporary administrator account created for your AzuraCast instance. You can remove this account whenever you like once this issue is resolved.
If you prefer a more secure method of communicating this information, you can also reach me via KeyBase and share files or other details securely with me through that application.
(Note: though I do occasionally ask that people send me e-mails for the purpose of diagnosing specific AzuraCast issues, please _do not_ contact me directly via e-mail for general problems or questions, unless asked to do so via Github issues. Thank you!)
Thanks for the help.I reinstalled the vps all fresh again and it's working now.Don't what actually happend i was getting the error.