Hi,
I noticed the same problem about a week ago, so it was easy to fix it
(again) by deleting two excessively large log files in /var/log/jenkins,
with log messages caused by the jmdns library.
So far, I didn't have time to investigate the root cause. This is likely
to occur again, but now at least we have a clue how to reclaim space.
Cheers,
Harald
Am 12.05.2015 um 20:36 schrieb Achim Nierbeck:
> Hi,
>
> oops totally forgot ... :)
>
> will try to find out what stuff to delete.
>
> regards, Achim
>
>
> 2015-05-12 20:24 GMT+02:00 Toni Menzel <
toni....@rebaze.com
> <mailto:
toni....@rebaze.com>>:
>
> Will have access to the box tomorrow earliest since i do not have
> the private key on a new-ish box traveling with.
> @Harald?
> @Achim, looking at past emails (from 2013) i know i have granted you
> ssh access. Emails title "ssh on build server". So maybe you just
> try log in?
>
> *Toni Menzel*
>
> *
> *
>
> *Are you curious? Follow us <
https://twitter.com/rebazeio>**
> *
>
> *rebaze GmbH | *
http://www.rebaze.de | Twitter @rebazeio
> <
https://twitter.com/rebazeio>| LinkedIn Profile
> <
http://www.linkedin.com/company/2553599>
> <mailto:
ops4j-infra...@googlegroups.com>.
> <mailto:
ops4j-infra...@googlegroups.com>.
> --
> You received this message because you are subscribed to the Google
> Groups "OPS4J Infrastructure" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
ops4j-infra...@googlegroups.com
> <mailto:
ops4j-infra...@googlegroups.com>.