some obscure idea made me mount /var/log in tmpsfs. probably when
experimenting with my new ssd.
problem solved.
MartinK's Profile: http://forums.slimdevices.com/member.php?userid=66540
View this thread: http://forums.
MartinK wrote:
> My problem in indeed related to the missing log files. Every time I
> reboot the directory /var/log/squeezeboxserver disappears. If I manually
> create a directory and a stub for server.log and start LMS manually
> everything is fine.
>
> How strange is that? Apart from samba t
My problem in indeed related to the missing log files. Every time I
reboot the directory /var/log/squeezeboxserver disappears. If I manually
create a directory and a stub for server.log and start LMS manually
everything is fine.
How strange is that? Apart from samba there is nothing running on m
more output:
root@sbox:~# /usr/sbin/squeezeboxserver --prefsdir
/var/lib/squeezeboxserver/prefs --logdir /var/log/squeezeboxserver
--cachedir /var/lib/squeezeboxserver/cache --charset=utf8 --d_server
--debug server
Async::HTTP: Unable to load IO::Socket::SSL, will try connecting to SSL
servers i
I really think you should start to investigate why your log and cache
folders disappear. LMS failing is just a side-effect.
--
Michael
___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
this looks like the same problem i'm having??
Thread: Perl problems with LMS 7.9 on Debian sid
MartinK's Profile: http://forums.slimdevices.com/member.php?userid=66540
View this thread: http://forums.slimdevices.com/showth
I tried to run the server from the console it stops because of some
error from CPAN
root@sbox:~# /usr/sbin/squeezeboxserver --prefsdir
/var/lib/squeezeboxserver/prefs --logdir /var/log/squeezeboxserver/
--cachedir /var/lib/squeezeboxserver/cache --charset=utf8 --d_server
Async::HTTP: Unable to l
settings like in the deb control files. After a reboot both files are
gone. Seems like some cleanup is happening somewhere.
But that's something somewhere in your system, not in LMS.
Worst case you could re-direct those folders to some other folder of
your choice, defining the paths in the sta
Meanwhile I have looked at the installation .deb file and executed all
the steps manually. (copied the files and and did all the control
instructions). Surprising that gave me a running system. But still it
doesn't persist after reboot. Somewhere in the boot process (or
shutdown) files from /var/l
I copied the full command string and appended --d_startup --debug >>
dump.log
And it kept running? It didn't stop? Please run the same command again
without the --daemon or & (if any) so it stays in the terminal window.
Would it just continue to run? Or would you get any failure?
--
Michael
the only things awkward are:
Async::HTTP: Unable to load IO::Socket::SSL, will try connecting to SSL
servers in non-SSL mode
[17-01-25 16:52:54.3419] main::init (388) Starting Logitech Media Server
(v7.9.0, 1484464959, Mon Jan 23 04:38:38 UTC 2017) perl 5.022002 -
x86_64-linux-gnu-thread-multi
[
21972
this is what I get when LMS runs but I can't connect.
+---+
|Filename: Screenshot from 2017-01-25 15-22-03.png |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=21972|
+--
I copied the full command string and appended --d_startup --debug >>
dump.log
this is dump.log:
Found SELinux - setting security context to: texrel_shlib_t for *.so
files.
Got @INC containing:
/usr/share/squeezeboxserver/CPAN
/usr/share/squeezeboxserver
/usr/sbin
/etc/perl
/usr/local/lib/x86_64
I have also noticed that the 7.9 installation script does not generate a
new init.d/logitechmediaserver startup script like all the old version
used to do (7.7, 7.8). It does however, update an existing file if one
exists but it does not generate a new one. As a result I'm not quite
sure if the fi
I don't know how to do that. You you mean using a similar command than
the one in init.d/logitechmediaserver and run it as a console task
without all the extra bits?
Yes, just run the command:
/usr/sbin/logitechmediaserver
in a terminal window (please adjust the path and filename accordingly..
mherger wrote:
> > LMS_safe = 'logitechmediaserver' plus the '_safe' suffix. Which
>
> The _safe task is a process watcher which would restart the main task if
>
> needed. You should always see both of them, or something's wrong.
>
> I think the LMS executable is stored in /usr/sbin or /usr/lo
LMS_safe = 'logitechmediaserver' plus the '_safe' suffix. Which
The _safe task is a process watcher which would restart the main task if
needed. You should always see both of them, or something's wrong.
I think the LMS executable is stored in /usr/sbin or /usr/local/sbin.
Could you try to ru
Ok I think we are getting away from the point a little here.
A couple of things: init.d still works, systemd is required to run
non-compliant init.d scripts just like before. Unless someone has
modified the LMS startup to deliberately bolt into systemd then its
behaviour will still be dictated by
MartinK wrote:
> Apart from that there have been absolutely no hacks on the system.
ok - just thought there is some text like > deleting the user and group
settings everything and as admin@work i do really know the stories from the
customers who
told me "i didnt change anything" so i tought i
DJanGo wrote:
> Ubuntu 16.10 (Yakkety Yak) was released @ 13.10.2016 your*- forever
> -*seems not long ago?
>
> port 9000 is used from the webfrontend not from telnet.
>
>
> ok thats a pretty strange idea - i would not recommend that...
>
> I would say - your system has some nice -addons- / -
MartinK wrote:
> i've recently updated my old LMS installation to 7.9 on my ubuntu server
> (16.10) which i've had forever.
Ubuntu 16.10 (Yakkety Yak) was released @ 13.10.2016 your*- forever
-*seems not long ago?
> But still telneting into port 9000 shows connection refused port 9000 is used
drmatt wrote:
> (I believe LMS_safe is the parent script that kicks off the main
> daemons. It's what you might see in the process table if LMS main thread
> fails to start. I've seen this a few times when I was fighting Perl
> version mismatches.. :) )
Perl on my system (ubuntu64 16.10)
This i
Sorry for not being more specific.
The system is intel based D510MO board with 2 x1TB disks. LVM
configuration. There are no errors in the system logs.
LMS_safe = 'logitechmediaserver' plus the '_safe' suffix. Which
apparently is needed to reconnect to mysql if I correctly understood the
code
(I believe LMS_safe is the parent script that kicks off the main
daemons. It's what you might see in the process table if LMS main thread
fails to start. I've seen this a few times when I was fighting Perl
version mismatches.. :) )
--
Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver
everything !! However, when I reboot LMS comes up as LMS_safe and I can
What is this LMS_safe?
no longer connect to port 9000. Although, the server appears to be
running. There is no firewall and I can ping the outside world in all
How do you find out about the server being active?
directi
i've recently updated my old LMS installation to 7.9 on my ubuntu server
(16.10) which i've had forever. After doing the installation everything
works perfectly - music found, prefs found, player found, scan perfect,
everything !! However, when I reboot LMS comes up as LMS_safe and I can
no longer
26 matches
Mail list logo
