Oops. My error. 8082 is OAI port, not PUI.
Not sure how far back OAI support was initially added.
> On Nov 12, 2018, at 2:02 PM, Majewski, Steven Dennis (sdm7g)
> wrote:
>
>
> The default ports haven’t changed.
> Blake transposed digits in his email to 8028, but the error message says
>
The default ports haven’t changed.
Blake transposed digits in his email to 8028, but the error message says 8082,
which is the default port for public webapp.
Default port numbers are in common/config/config-defaults.rb:
Blake,
What port did it run on before 2.5?
Rick
Sent from my iPhone
On Nov 12, 2018, at 11:39 AM, Blake Carver wrote:
>>> WARNING: FAILED SelectChannelConnector@0.0.0.0:8082:
>>> java.net.BindException: Address already in use
>
> Something is running on port 8028 already so ArchivesSpace
Dear colleagues,
I'm writing to ask if anyone is using ArchivesSpace event records to track
digitization work performed on collection materials. For example, I could see
indicating digitization status by attaching event records to particular
archival components and/or resources. If you're
>>WARNING: FAILED SelectChannelConnector@0.0.0.0:8082: java.net.BindException:
>>Address already in use
Something is running on port 8028 already so ArchivesSpace can't start up since
that's being used now.
From:
Good morning,
I successfully upgraded our version of ArchiveSpace on my test server to
version 2.5 with no issues.
I am now trying to replicate it on my production server.
After my upgrade I restarted the service and the staff and public interfaces
won’t display in a browser although the
