[JIRA] (JENKINS-57211) Jenkins won't start due to some User Migration Exception.

2 views
Skip to first unread message

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 29, 2019, 12:40:02 AM4/29/19
to jenkinsc...@googlegroups.com
Oleg Nenashev moved an issue
 
Jenkins / Bug JENKINS-57211
Jenkins won't start due to some User Migration Exception.
Change By: Oleg Nenashev
Project: Infrastructure Jenkins
Key: INFRA JENKINS - 2070 57211
Workflow: classic default workflow JNJira + In-Review
Component/s: core
Component/s: core
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

o.v.nenashev@gmail.com (JIRA)

unread,
May 3, 2019, 8:07:02 AM5/3/19
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
May 3, 2019, 8:07:02 AM5/3/19
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
May 3, 2019, 8:07:02 AM5/3/19
to jenkinsc...@googlegroups.com

dbeck@cloudbees.com (JIRA)

unread,
May 3, 2019, 8:11:01 AM5/3/19
to jenkinsc...@googlegroups.com

/opt/jenkins is not an official Docker container path.

I wonder whether NFS or a similarly shitty FS are involved.

jthompson@cloudbees.com (JIRA)

unread,
May 3, 2019, 12:00:03 PM5/3/19
to jenkinsc...@googlegroups.com

This sounds like the same thing discussed on the user email list at https://groups.google.com/d/msg/jenkinsci-users/h-Eku3NnWLg/le9Xx_a4CQAJ . In that case it did turn out to be connected to underlying filesystem problems. We saw a number of filesystem errors in the logs and other similar problems in other software. In that case, the user was able to run on a different system and avoid the problems entirely.

If you can, try running the same upgrade on a different system with a more stable filesystem. Or reconfigure your environment to make the filesystem more stable. We would need lot more information about the environment and the logs before we could diagnose anything further.

jthompson@cloudbees.com (JIRA)

unread,
Jun 11, 2019, 5:46:02 PM6/11/19
to jenkinsc...@googlegroups.com
Jeff Thompson closed an issue as Cannot Reproduce
 

Since there has been a lack of response for quite a while on this, I'm going to close this issue. If you have additional information to help move this along, feel free to provide it and re-open as needed.

Change By: Jeff Thompson
Status: Open Closed
Resolution: Cannot Reproduce
Reply all
Reply to author
Forward
0 new messages