hgalt
commented
1 year ago @karlheyes
I figured out, that I am using different setups for paths.
<logdir>./logs</logdir>
or
<logdir>.\logs</logdir>
or
<logdir>.\logs\</logdir>
Has it something to do with Windows? I am using a Windows server, so wich one should I use?
If I change <logdir in the icecast.xml will it be change with Reload Config or only if I restart the service?
Karl,
I have figured out some problems with an clean installation of the kh22 and kh21.6.
With clean installation, I mean, I have deleated the whole folder of IcecastKH. I did this, because I did run into some problems, that the services was not starting after reboot with 21.6. So I decided to to install the newest version kh22. I also had the same problems and uninstalled kh22, deleted the whole folder and rebooted the machine before I installed kh22 again. Now the services was starting correct, but with kh22 I was running into ssl problems. The error.log reported an error with the certificate. But Icecast 2.4.4 was able to use the same certificate without any problems. Also kh22 did not write to the error.log and access.log file.
After that I decided to reinstall kh21.6, which was running before without any problem with the ssl-certificate. So I did a clean installation with kh21.6 again. The ssl-certificate problems are gone, but still no error.log and access.log will be generated. I only can see an error.log and access.log in the web interface.
Looking into the Error Log, I could not find any message which would help me for the missing log files. But I could see, that there was a message, that the mime.types file could not be found. After I copied the mime.types file from my 2.4.4 installation to the icecastkh folder, this message is no gone.
What could be the reason, that no error.log and access.log file are generated?