mherger wrote:
> > Looks like postgresql is the culprit but as you say 45 mb is not very
> > much
>
> What I meant to say was that I believe 45M for a partition to store logs
>
> on was not not enough. LMS logs can get quite big, too.
I knew what you meant - I'll look into expanding the
Looks like postgresql is the culprit but as you say 45 mb is not very
much
What I meant to say was that I believe 45M for a partition to store logs
on was not not enough. LMS logs can get quite big, too.
___
discuss mailing list
mherger wrote:
> >> Should probably have said "du -hsc /var/log/" (with the slash at the
> >> end).
> >
> > The slash at the end made no difference
> > 45M /var/log/
> > 45M total
>
> I'm sorry, got this wrong twice already... "du -hsc /var/log/*". Or "ls
>
> -al /var/log/"
0
Should probably have said "du -hsc /var/log/" (with the slash at the
end).
The slash at the end made no difference
45M /var/log/
45M total
I'm sorry, got this wrong twice already... "du -hsc /var/log/*". Or "ls
-al /var/log/"
___
discuss
mherger wrote:
> Should probably have said "du -hsc /var/log/" (with the slash at the
> end).
The slash at the end made no difference
45M /var/log/
45M total
Nanopi M4V2 Debian 4gb RAM 1TB SSD -> LMS -> Squeezelite -> Sablon EVO
USB -> SRCDX -> Wave Storm BNC -> Chord Hugo MScaler ->
Should probably have said "du -hsc /var/log/" (with the slash at the
end).
Michael
"It doesn't work - what shall I do?" - "Please check your server.log
and/or scanner.log file!"
(LMS: Settings/Information)
mherger's
mherger wrote:
> > Filesystem Size Used Avail Use% Mounted on
> > /dev/zram1 49M 45M 0 100% /var/log
> >
> > There are no large files in /var/log - any ideas guys ?
>
> 45MB is not a lot. What does "du -hsc /var/log" say?
Hi Michael
45M /var/log
45M
Filesystem Size Used Avail Use% Mounted on
/dev/zram1 49M 45M 0 100% /var/log
There are no large files in /var/log - any ideas guys ?
45MB is not a lot. What does "du -hsc /var/log" say?
___
discuss mailing list
Hi all, I have had LMS running on a Linux SBC for years without any
problems, I recently noticed the server had stopped and running
systemctl status logitechmediaserver.service from a terminal gives me
this
Cannot write to '/var/log/squeezeboxserver/server.log': No space left on
device at
I just istalled SlimServer 6.5 on a clean install of Windows Media
Center. It was the first app installed, but I can't get it to start -
the tray icon just says starting slimserver continually.
I did install Alien BBC immediately after, and before starting Slim,
but that seemed to istall
I came across this message, and a few others, and thought that I might
just be able to uninstall and reinstall. No luck. I went to the log
file, and found the following associated with the repeated stopping of
the server after just a few seconds:
mkdir /Users/brianmccardel/Music/Playlists:
Check your Library - Logs - slimserver.log file. There should be
an error message at the end indicating what went wrong.
Alternatively, get in touch with [EMAIL PROTECTED] to walk you
through this...
On Jun 24, 2006, at 8:57 AM, holderlin wrote:
I have Slim Server set to start at start
I have Slim Server set to start at start up. It doesn't start. When I
press Start Server, it goes to stop server for a few seconds then
returns to Start Server. Web access is also disabled.
Any thoughts?
Thanks,
Bob
--
holderlin
I forgot to add that I'm using v6.2.2 on a Mac running 10.4.6
When I go to systems profiler/startup items, here's the description:
Description:SlimServer
Location: /Library/StartupItems/Slim
Provides: SlimServer
Requires: Disks
Uses: mDNSResponder, Resolver,
I installed v6.3. Same problem.
Bob
--
holderlin
holderlin's Profile: http://forums.slimdevices.com/member.php?userid=4821
View this thread: http://forums.slimdevices.com/showthread.php?t=24958
15 matches
Mail list logo
