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 среда, 18. октобар 2023. у 13:33:59 UTC+2 Milos Ivanovic је написао/ла: > Many thanks, @Leandro, I will give it a try. > > Kind regards > Milos > > уторак, 17. октобар 2023. у 15:14:05 UTC+2 Leandro Pereira је написао/ла: > >> [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 >> >> Em terça-feira, 17 de outubro de 2023 às 09:06:14 UTC-3, Milos Ivanovic >> escreveu: >> >>> 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 >>> >>> >>> недеља, 15. октобар 2023. у 10:04:21 UTC+2 Milos Ivanovic је написао/ла: >>> >>>> Thanks @leandro for your quick reply. Unfortunately, this is something >>>> different. The table *systemwidealert* is empty :( >>>> >>>> >>>> недеља, 15. октобар 2023. у 04:44:21 UTC+2 Leandro Pereira је >>>> написао/ла: >>>> >>>>> 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; >>>>> >>>>> Em sexta-feira, 13 de outubro de 2023 às 15:45:57 UTC-3, Milos >>>>> Ivanovic escreveu: >>>>> >>>>>> 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 >>>>>> >>>>>> -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/57194ec6-0855-48ab-8528-4be0f54378can%40googlegroups.com.
