Red box above the frame in DSpace 7.6

106 views
Skip to first unread message

Milos Ivanovic

unread,
Oct 13, 2023, 2:45:57 PM10/13/23
to DSpace Technical Support
Dear All,

I use the 7.6 release and everything works well so far. However, last week, upon the server restart, the thin horizontal box appeared out of nowhere, just above the whole frame. It looks like an empty alert box (image provided). What can it be and how to remove it?

Something like this in HTML:

<div _ngcontent-dspace-angular-c211="" class="ng-star-inserted"><div _ngcontent-dspace-angular-c211="" class="rounded-0 alert alert-warning w100"><div _ngcontent-dspace-angular-c211="" class="container"><span _ngcontent-dspace-angular-c211="" class="font-weight-bold"><!--bindings={
  "ng-reflect-ng-if": "false"
}--><!--bindings={
  "ng-reflect-ng-if": "false"
}--><!--bindings={
  "ng-reflect-ng-if": "false"
}--><!--bindings={
  "ng-reflect-ng-if": "false"
}--></span><span _ngcontent-dspace-angular-c211=""></span></div></div></div>

Thanks in advance,
Milos

Screenshot from 2023-10-13 20-37-09.png

Leandro Pereira

unread,
Oct 14, 2023, 10:44:21 PM10/14/23
to DSpace Technical Support
Hi

had the same problem. It normally happens when the system maintenance button is active. However in the version, some bug prevents deactivation, not yet resolved.

Wu solved the same problem by deleting the alert from the database.

~# psql dspace
psql (14.9)
Type "help" for help.

dspace=# delete from systemwidealert;

Milos Ivanovic

unread,
Oct 15, 2023, 4:04:21 AM10/15/23
to DSpace Technical Support
Thanks @leandro for your quick reply. Unfortunately, this is something different. The table systemwidealert is empty :(

Milos Ivanovic

unread,
Oct 17, 2023, 8:06:14 AM10/17/23
to DSpace Technical Support
The appearance of this box may have to do something with another problem. Every few days DSpace backend just stops, with the following output:

$ tail catalina.out
[2023-10-17 02:35:05] [info] [546663.224s][warning][os,thread] Failed to start the native thread for java.lang.Thread "Connection evictor"
[2023-10-17 02:35:30] [info] [546688.070s][warning][os,thread] Failed to start thread "Unknown thread" - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached.
[2023-10-17 02:35:30] [info] [546688.071s][warning][os,thread] Failed to start thread "Unknown thread" - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached.
[2023-10-17 02:35:30] [info] [546688.072s][warning][os,thread] Failed to start the native thread for java.lang.Thread "Connection evictor"
[2023-10-17 02:35:30] [info] [546688.072s][warning][os,thread] Failed to start thread "Unknown thread" - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached.
[2023-10-17 02:35:30] [info] [546688.072s][warning][os,thread] Failed to start the native thread for java.lang.Thread "Connection evictor"
[2023-10-17 02:35:30] [info] [546688.073s][warning][os,thread] Failed to start the native thread for java.lang.Thread "Connection evictor"
[2023-10-17 02:35:32] [info] [546690.312s][warning][os,thread] Failed to start thread "Unknown thread" - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached.
[2023-10-17 02:35:32] [info] [546690.313s][warning][os,thread] Failed to start the native thread for java.lang.Thread "Connection evictor"
[2023-10-17 02:35:32] [info] [546690.314s][warning][os,thread] Failed to start thread "Unknown thread" - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached.
[2023-10-17 02:35:32] [info] [546690.314s][warning][os,thread] Failed to start the native thread for java.lang.Thread "Connection evictor"
[2023-10-17 02:35:32] [info] [546690.315s][warning][os,thread] Failed to start thread "Unknown thread" - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 0k, detached.
[2023-10-17 02:39:28] [info] [546926.143s][warning][os,thread] Failed to start the native thread for java.lang.Thread "http-nio-0.0.0.0-8080-exec-499"
[2023-10-17 02:39:28] [info] Exception in thread "http-nio-0.0.0.0-8080-Poller" java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached
[2023-10-17 02:39:28] [info] #011at java.base/java.lang.Thread.start0(Native Method)
[2023-10-17 02:39:28] [info] #011at java.base/java.lang.Thread.start(Thread.java:798)
[2023-10-17 02:39:28] [info] #011at org.apache.tomcat.util.threads.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:984)
[2023-10-17 02:39:28] [info] #011at org.apache.tomcat.util.threads.ThreadPoolExecutor.executeInternal(ThreadPoolExecutor.java:1480)
[2023-10-17 02:39:28] [info] #011at org.apache.tomcat.util.threads.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1402)
[2023-10-17 02:39:28] [info] #011at org.apache.tomcat.util.threads.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1376)
[2023-10-17 02:39:28] [info] #011at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1174)
[2023-10-17 02:39:28] [info] #011at org.apache.tomcat.util.net.NioEndpoint$Poller.processKey(NioEndpoint.java:867)
[2023-10-17 02:39:28] [info] #011at org.apache.tomcat.util.net.NioEndpoint$Poller.run(NioEndpoint.java:834)
[2023-10-17 02:39:28] [info] #011at java.base/java.lang.Thread.run(Thread.java:829)


The server has 24GB RAM, so it cannot be a problem. Ther health status reported by DSpace is okay, as well as the dspace.log output. Any idea where to look?

Thanks in advance,
Milos

Leandro Pereira

unread,
Oct 17, 2023, 9:14:05 AM10/17/23
to DSpace Technical Support
[2023-10-17 02:39:28] [info] Exception in thread "http-nio-0.0.0.0-8080-Poller" java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached

Maybe this post reseolve the problem:
https://stackoverflow.com/questions/72477454/java-lang-outofmemoryerror-unable-to-create-native-thread-possibly-out-of-mem

Milos Ivanovic

unread,
Oct 18, 2023, 7:33:59 AM10/18/23
to DSpace Technical Support
Many thanks, @Leandro, I will give it a try.

Kind regards
Milos

Milos Ivanovic

unread,
Oct 24, 2023, 9:08:42 AM10/24/23
to DSpace Technical Support
Just to let you know about the epilogue. It was just an accidentally turned-on System alert with an empty string. Upon turning it off, everything seems ok. A suggestion to the developers: Prohibit empty status strings for system-wide alerts to prevent such behavior.

Regards
Milos
Reply all
Reply to author
Forward
0 new messages