CompreFace crashes upon starting up #1276
Unanswered
mdaraujoGit
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all.
Since last night my compreFace installation is behaving errratically consumming a large % of the CPU
And, upon checking the log, it seems that the solution failed to startup.
I have already tried stopping and restarting CompreFace, restarting HomeAssistant and yet, the error persists.
I really would like to avoid to uninstall and again install the solution as I would have to again, train all the faces which is not ideal...
Thank you for any possible help:
2024-10-17 10:18:05,966 INFO exited: compreface-postgres-db (exit status 1; not expected)
{"severity": "INFO", "message": "{'BUILD_VERSION': 'dev', 'CALCULATION_PLUGIN': 'facenet.Calculator', 'EXTRA_PLUGINS': ['facenet.LandmarksDetector', 'agegender.AgeDetector', 'agegender.GenderDetector', 'facenet.facemask.MaskDetector', 'facenet.PoseEstimator'], 'FACE_DETECTION_PLUGIN': 'facenet.FaceDetector', 'GPU_IDX': -1, 'IMG_LENGTH_LIMIT': 640, 'INTEL_OPTIMIZATION': False, 'IS_DEV_ENV': False, 'LOGGING_LEVEL_NAME': 'DEBUG', 'ML_PORT': 3000, 'RUN_MODE': True}", "request": null, "logger": "src.app", "module": "app", "traceback": null, "build_version": "dev"}
2024-10-17 10:18:05,982 INFO spawned: 'compreface-postgres-db' with pid 55
{"severity": "DEBUG", "message": "Creating new app for WSGI", "request": null, "logger": "src.app", "module": "app", "traceback": null, "build_version": "dev"}
2024-10-17 10:18:05,982 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x558af0167fb0 pid: 15 (default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 15)
spawned uWSGI worker 1 (pid: 56, cores: 1)
2024-10-17 09:18:05.992 UTC [55] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:05.992 UTC [55] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:05,994 INFO exited: compreface-postgres-db (exit status 1; not expected)
spawned uWSGI worker 2 (pid: 57, cores: 1)
2024-10-17 10:18:05,997 INFO spawned: 'compreface-postgres-db' with pid 58
2024-10-17 09:18:06.005 UTC [58] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:06.005 UTC [58] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:06,005 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:06,006 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:07,008 INFO spawned: 'compreface-postgres-db' with pid 59
2024-10-17 09:18:07.023 UTC [59] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:07.023 UTC [59] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:07,024 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:07,024 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:08,026 INFO spawned: 'compreface-postgres-db' with pid 60
2024-10-17 09:18:08.041 UTC [60] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:08.041 UTC [60] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:08,041 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:08,042 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:09,044 INFO spawned: 'compreface-postgres-db' with pid 61
2024-10-17 09:18:09.053 UTC [61] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:09.053 UTC [61] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:09,054 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:09,054 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:10,056 INFO spawned: 'compreface-postgres-db' with pid 62
2024-10-17 09:18:10.071 UTC [62] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:10.071 UTC [62] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:10,071 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:10,072 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:11,075 INFO spawned: 'compreface-postgres-db' with pid 63
2024-10-17 09:18:11.094 UTC [63] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:11.094 UTC [63] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:11,094 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:11,095 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:12,099 INFO spawned: 'compreface-postgres-db' with pid 64
2024-10-17 09:18:12.118 UTC [64] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:12.118 UTC [64] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:12,119 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:12,119 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:13,123 INFO spawned: 'compreface-postgres-db' with pid 65
2024-10-17 09:18:13.149 UTC [65] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:13.149 UTC [65] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:13,149 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:13,150 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:14,153 INFO spawned: 'compreface-postgres-db' with pid 66
2024-10-17 09:18:14.169 UTC [66] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:14.169 UTC [66] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:14,169 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:14,170 INFO exited: compreface-postgres-db (exit status 1; not expected)
Starting compreface-admin
2024-10-17 10:18:14,951 INFO spawned: 'compreface-postgres-db' with pid 68
2024-10-17 09:18:14.969 UTC [68] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:14.969 UTC [68] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:14,970 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:14,971 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:15,049 INFO spawned: 'compreface-postgres-db' with pid 69
2024-10-17 10:18:15,051 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:15,053 INFO spawned: 'compreface-admin' with pid 70
2024-10-17 10:18:15,053 INFO success: compreface-admin entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
compreface-admin: started
2024-10-17 09:18:15.060 UTC [69] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:15.060 UTC [69] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:15,061 INFO exited: compreface-postgres-db (exit status 1; not expected)
. ____ _ __ _ _
/\ / ' __ _ () __ __ _ \ \ \
( ( )__ | '_ | '| | ' / ` | \ \ \
2024-10-17 10:18:15,948 INFO spawned: 'compreface-postgres-db' with pid 108
\/ )| |)| | | | | || (| | ) ) ) )
' || .__|| ||| |_, | / / / /
2024-10-17 10:18:15,949 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
=========||==============|/=////
:: Spring Boot :: (v2.5.13)
2024-10-17 09:18:15.968 UTC [108] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:15.968 UTC [108] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:15,972 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:16.027 INFO 70 --- [kground-preinit] o.h.validator.internal.util.Version : HV000001: Hibernate Validator 6.2.3.Final
2024-10-17 10:18:16,030 INFO spawned: 'compreface-postgres-db' with pid 109
2024-10-17 09:18:16.041 UTC [109] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:16.041 UTC [109] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:16,041 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:18:16,042 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:18:16.042 INFO 70 --- [ main] com.exadel.frs.FrsApplication : Starting FrsApplication v0.0.1-SNAPSHOT using Java 11.0.16 on c7657554-compreface with PID 70 (/app/admin/app.jar started by root in /app/admin)
2024-10-17 10:18:16,044 INFO spawned: 'compreface-postgres-db' with pid 110
2024-10-17 10:18:16.043 DEBUG 70 --- [ main] com.exadel.frs.FrsApplication : Running with Spring Boot v2.5.13, Spring v5.3.19
2024-10-17 10:18:16.043 INFO 70 --- [ main] com.exadel.frs.FrsApplication : The following 1 profile is active: "dev"
2024-10-17 10:18:16,044 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 09:18:16.051 UTC [110] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:18:16.051 UTC [110] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:18:16,052 INFO exited: compreface-postgres-db (exit status 1; not expected)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:448)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:339)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1365)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1354)
at com.exadel.frs.TrainServiceApplication.main(TrainServiceApplication.java:31)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:108)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
2024-10-17 10:19:01,663 INFO spawned: 'compreface-postgres-db' with pid 761
2024-10-17 10:19:01.661 INFO 688 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting...
2024-10-17 10:19:01,664 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:5432
Caused by: java.net.ConnectException: Connection refused
at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777)
at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:710)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:658)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:584)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:496)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at java.base/java.lang.Thread.run(Thread.java:829)
2024-10-17 10:19:01.670 WARN 605 --- [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'notificationReceiverService': Invocation of init method failed; nested exception is java.lang.NullPointerException
2024-10-17 10:19:01.673 INFO 605 --- [ main] j.LocalContainerEntityManagerFactoryBean : Closing JPA EntityManagerFactory for persistence unit 'default'
2024-10-17 10:19:01.687 INFO 605 --- [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat]
2024-10-17 09:19:01.691 UTC [761] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:19:01.691 UTC [761] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:19:01.714 INFO 605 --- [ main] ConditionEvaluationReportLoggingListener :
Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2024-10-17 10:19:01,715 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:19:01.742 ERROR 605 --- [ main] o.s.boot.SpringApplication : Application run failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'notificationReceiverService': Invocation of init method failed; nested exception is java.lang.NullPointerException
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:160)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:440)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1796)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:620)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:953)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583)
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145)
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775)
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:448)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:339)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1365)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1354)
at com.exadel.frs.TrainServiceApplication.main(TrainServiceApplication.java:31)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:108)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
Caused by: java.lang.NullPointerException: null
at com.exadel.frs.core.trainservice.service.NotificationReceiverService.setUpNotification(NotificationReceiverService.java:69)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:389)
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:333)
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:157)
... 26 common frames omitted
2024-10-17 10:19:01,745 INFO spawned: 'compreface-postgres-db' with pid 762
2024-10-17 09:19:01.764 UTC [762] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:19:01.764 UTC [762] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:19:01,765 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:19:01,766 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:19:02,124 INFO spawned: 'compreface-postgres-db' with pid 765
2024-10-17 10:19:02,124 INFO exited: compreface-api (exit status 1; not expected)
2024-10-17 09:19:02.140 UTC [765] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:19:02.140 UTC [765] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:19:02,141 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:19:02,142 INFO spawned: 'compreface-api' with pid 766
2024-10-17 10:19:02,142 INFO exited: compreface-postgres-db (exit status 1; not expected)
2024-10-17 10:19:02,143 INFO spawned: 'compreface-postgres-db' with pid 767
2024-10-17 10:19:02,144 INFO success: compreface-api entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 09:19:02.151 UTC [767] FATAL: lock file "postmaster.pid" is empty
2024-10-17 09:19:02.151 UTC [767] HINT: Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2024-10-17 10:19:02,151 INFO success: compreface-postgres-db entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-17 10:19:02,152 INFO exited: compreface-postgres-db (exit status 1; not expected)
Beta Was this translation helpful? Give feedback.
All reactions