I saw this as well. I manually created /var/run/jenkins (owned by the jenkins user) and finished the package update.
----- Original Message ----- From: [email protected] To: [email protected] At: Nov 6 2013 00:21:03 Hello I got following error while upgrading from 1.537 -> 1.538 on Ubuntu: Preparing to replace jenkins 1.537 (using .../archives/jenkins_1.538_all.deb) ... * Stopping Jenkins Continuous Integration Server jenkins [ OK ] Unpacking replacement jenkins ... Processing triggers for ureadahead ... Setting up jenkins (1.538) ... chown: cannot access `/var/run/jenkins': No such file or directory dpkg: error processing jenkins (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: jenkins E: Sub-process /usr/bin/dpkg returned an error code (1) As a result, Jenkins didn't start. Jenkins started properly with "service jenkins start", though. So this is kind of FYI, I don't know if there's any bigger problems or if this was some quirk in my system. -Jyrki-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
