Shibboleth 3.3.1 install on brand new Windows Server

[Steven Teixeira]

I was planning on keeping an eye out and doing a bit more testing, just wondered if anyone else had run into this yet.

Steven Teixeira

From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Rod Widdowson
Sent: Thursday, March 23, 2017 3:34 AM
To: 'Shib Users' <users at shibboleth.net>
Subject: RE: Shibboleth 3.3.1 install on brand new Windows Server

That's extremely weird since there should be absolutely not difference between the 3.3.1 and 3.3.0 in this area.  I was pretty sure that they ship the same jetty - and this looks like a jetty issue (although why the upgrade works is also a mystery).

I'll try to repro (I must have a SRV2012 kicking around somewhere).

Meanwhile I'd concur that a 3.3.0 install and a 3.3.1 upgrade is the best way to go.  But make sure that you do a full reboot and test that the upgrade "took" (bin\status) before you declare victory.  Services have a habit of hanging around if you are not careful.

From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Steven Teixeira
Sent: 23 March 2017 00:02
To: Shib Users
Subject: Shibboleth 3.3.1 install on brand new Windows Server

Has anyone tried installing Shibboleth 3.3.1 on a brand new Windows Server(2012R2)?  Our upgrade from 3.3.0 to 3.3.1 in our non-production environment seems to work, but when I attempt to install on a brand new server, the Windows Service never starts after install, or after a reboot, and also fails to start manually.  I've tried the 3.3.1 installation a few times, and installing 3.3.0 doesn't seem to have this issue, but I'm not sure if I'm missing something or doing something differently and not realizing it.  Since the upgrade seems to work, I suppose we can upgrade in production, but not having it work on a new server makes me cautious to finish deploying to production if there's more going on I haven't seen/found yet.

The only error log I've been able to find is in ProcRun\log and says(the properties file that's referenced changes with every start attempt):

2017-03-22 15:21:11 Commons Daemon procrun stderr initialized
java.nio.file.NoSuchFileException: C:\Program Files (x86)\Shibboleth\IdP\jetty-base\tmp\start_6520181791236828906.properties
                at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
                at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
                at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
                at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(Unknown Source)
                at java.nio.file.Files.newByteChannel(Unknown Source)
                at java.nio.file.Files.createFile(Unknown Source)
                at java.nio.file.TempFileHelper.create(Unknown Source)
                at java.nio.file.TempFileHelper.createTempFile(Unknown Source)
                at java.nio.file.Files.createTempFile(Unknown Source)
                at org.eclipse.jetty.start.StartArgs.getMainArgs(StartArgs.java:596)
                at org.eclipse.jetty.start.Main.invokeMain(Main.java:204)
                at org.eclipse.jetty.start.Main.start(Main.java:457)
                at org.eclipse.jetty.start.Main.main(Main.java:75)

Usage: java -jar start.jar [options] [properties] [configs]
       java -jar start.jar --help  # for more information

Steven Teixeira
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170323/9c431c92/attachment-0001.html>