Now that everything is passing again, I've re-enabled the smtp server. (And
thanks for disabling that over the weekend Andrea).

Notifications appear to going out successfully again.

Cheers,
Torben

On Mon, Jun 10, 2019 at 9:26 AM Torben Barsballe <
[email protected]> wrote:

> I have reprovisioned the worker nodes with more space, and builds are
> passing again. Its going to take a while to clear out the backlog of
> failing jobs, but everything should be back to normal.
>
> As far as I can tell, the master node still has sufficient space, it
> should just be the workers that were the issue.
>
> Torben
>
> On Sat, Jun 8, 2019 at 11:02 AM Jody Garnett <[email protected]>
> wrote:
>
>> Okay maybe a small clue, for a while we have been seeing at the top of
>> every build:
>>
>> ln builds/lastSuccessfulBuild
>> /var/lib/jenkins/jobs/geotools-release/lastSuccessful failed
>> java.nio.file.DirectoryNotEmptyException:
>> /var/lib/jenkins/jobs/geotools-release/lastSuccessful
>> ln builds/lastStableBuild
>> /var/lib/jenkins/jobs/geotools-release/lastStable failed
>> java.nio.file.DirectoryNotEmptyException:
>> /var/lib/jenkins/jobs/geotools-release/lastStable
>>
>>
>> I have been ignoring it as I was not sure if it was an expected warning
>> or not.
>>
>> Reading here https://issues.jenkins-ci.org/browse/JENKINS-48862 I see a
>> note: *My guess is that lastSuccessful and lastStable are actual
>> directories instead of symlinks (maybe because of a faulty backup/restore
>> that converted the symlinks into directories). A workaround would be to
>> delete those directories manually so that the next build can create the
>> symlinks correctly.*
>>
>> Could we have accidentally made lastSuccessful and lastStable into
>> directories (perhaps when trying to have links to the "latest" release?)
>>
>> I am still not sure if it is the jenkins build server or the worker which
>> is out of disk space.
>> --
>> Jody Garnett
>>
>>
>> On Sat, 8 Jun 2019 at 10:56, Jody Garnett <[email protected]> wrote:
>>
>>> Thanks Andrea, it appears it is out of disk space (so much so it cannot
>>> connect to a worker so it is failing very early in every build ...)
>>>
>>> Building remotely on FleetCloud i-097defbc6728da012 
>>> <https://build.geoserver.org/computer/i-097defbc6728da012> (linux-fleet) in 
>>> workspace /tmp/jenkins-45857990/workspace/geotools-release
>>> [ssh-agent] Looking for ssh-agent implementation...
>>> [ssh-agent]   Exec ssh-agent (binary ssh-agent on a remote machine)
>>> $ ssh-agent
>>> [ssh-agent]   Java/JNR ssh-agent
>>> ERROR: [ssh-agent] Could not register BouncyCastle on the remote agent.
>>> java.nio.file.FileSystemException: /tmp/resource-9284955164844191666: No 
>>> space left on device
>>>
>>>
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Sat, 8 Jun 2019 at 05:14, Andrea Aime <[email protected]>
>>> wrote:
>>>
>>>> Hi,
>>>> Jenkins has been bombarding the list for a while with failed builds
>>>> every few minutes, which apparently had no visible
>>>> trigger too. Not sure what's going on, but for the time being I've
>>>> removed the mail server configuration to hopefully
>>>> stop the mail shower.
>>>>
>>>> To enable it again to set the SMTP server back to smtp.gmail.com:
>>>>
>>>> [image: image.png]
>>>>
>>>> Cheers
>>>> Andrea
>>>>
>>>> == GeoServer Professional Services from the experts! Visit
>>>> http://goo.gl/it488V for more information. == Ing. Andrea Aime
>>>> @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054
>>>> Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339
>>>> 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it
>>>> ------------------------------------------------------- *Con
>>>> riferimento alla normativa sul trattamento dei dati personali (Reg. UE
>>>> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>>> precisa che ogni circostanza inerente alla presente email (il suo
>>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>>> This email is intended only for the person or entity to which it is
>>>> addressed and may contain information that is privileged, confidential or
>>>> otherwise protected from disclosure. We remind that - as provided by
>>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>>> e-mail or the information herein by anyone other than the intended
>>>> recipient is prohibited. If you have received this email by mistake, please
>>>> notify us immediately by telephone or e-mail.*
>>>> _______________________________________________
>>>> Geoserver-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>
>>> _______________________________________________
>> Geoserver-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to