On Sun, Mar 07, 2021 at 07:29:11PM +0000, Bouchard, Kerry wrote: > > Apparently starting dspace has been crashing the Oracle listener process when > the dspace server starts up. This is what our Oracle manager says he’s seeing > today: > > “The command service dspace start crashes the database if it is already > started. If the database is not started and you run the command it will > start the database but the database shuts down immediately. When I start the > database manually it stays up and running.”
Sounds like something for your Oracle manager to fix, then, unless he can show why DSpace is doing something specific that causes the crash. (If it's possible for a client to do *anything* that causes the DBMS instance to crash, Oracle should fix that.) One supposes that Oracle is logging some kind of errors as it goes down.... Possibly someone who is familiar with systemd could spot something that was damaged by the 'yum update'. The two units may be interfering with each other somehow. Anybody? > From: Bouchard, Kerry > Sent: Saturday, March 6, 2021 4:52 PM > > After more testing, I see that I can’t connect to the Oracle port on the > server even using “nc” > > nc localhost 1521 > Ncat: Connection refused. > > I’m thinking that on a working server, that wouldn’t be happening? I agree. > From: Bouchard, Kerry <[email protected]<mailto:[email protected]>> > Sent: Saturday, March 6, 2021 9:36 AM > > Caused by: java.net.ConnectException: Connection refused (Connection refused) > at java.net.PlainSocketImpl.socketConnect(Native Method) > at > java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) > at > java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) > at > java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:607) > at oracle.net.nt.TcpNTAdapter.connect(TcpNTAdapter.java:161) > at oracle.net.nt.ConnOption.connect(ConnOption.java:159) > at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:428) > ... 35 more The Oracle client could not open a connection to the DBMS because the DBMS is not listening on that port. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu -- All messages to this mailing list should adhere to the Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/YEZNPiZZsF2DAU/k%40IUPUI.Edu.
signature.asc
Description: PGP signature
