Unable to get Photoprism working

tsp001 · 4. April 2022

I am a beginner here. Read about this feature and it looks pretty good application to use. But having trouble setting it up. I have installed the photo prism plugin on omv6. When I try to configure the plugin I am getting this error. Need help with this.

albicocca · 4. April 2022

I encountered this problem too, but it was an error after upgrading the PhotoprisM version.

I have no clue at present. Similar problems have been encountered many times in OMV6, and it is also difficult to obtain a solution. I temporarily give up solving it and consider using other tools to replace it.

votdev · 4. April 2022

Will be fixed in next version. In the meanwhile simply create the directory ...../proxy/data mentioned in the error message.

aldobranti · 4. April 2022

This is openmediavault-photoprism 6.0.1-3 on

Release: 6.0.20-1
OS is debian bullseye on RPi4b with 8Gb ram

Photoprism will not stay alive

# systemctl status pod-photoprism.service

● pod-photoprism.service - Podman pod-photoprism.service

Loaded: loaded (/etc/systemd/system/pod-photoprism.service; enabled; vendor preset: enabled)

Active: active (running) since Mon 2022-04-04 10:30:37 BST; 5s ago

Process: 66166 ExecStartPre=/bin/rm -f /run/pod-photoprism.pid /run/pod-photoprism.pod-id (code=exited, status=0/SUCCESS)

Process: 66167 ExecStartPre=/usr/bin/podman pod create --infra-conmon-pidfile /run/pod-photoprism.pid --pod-id-file /run/pod-photoprism>

Process: 66198 ExecStart=/usr/bin/podman pod start --pod-id-file /run/pod-photoprism.pod-id (code=exited, status=0/SUCCESS)

Main PID: 66305 (conmon)

Tasks: 2 (limit: 8985)

CPU: 768ms

CGroup: /system.slice/pod-photoprism.service

└─66305 /usr/bin/conmon --api-version 1 -c 918c4fc99ba15ee7e68a7dd66008d30e01359597a238019b50d9a90c327899ce -u 918c4fc99ba15ee>

Apr 04 10:30:36 pi-vault systemd[1]: Starting Podman pod-photoprism.service...

Apr 04 10:30:36 pi-vault podman[66167]: 2022-04-04 10:30:36.458569394 +0100 BST m=+0.233314132 container create 918c4fc99ba15ee7e68a7dd6600>

Apr 04 10:30:36 pi-vault podman[66167]: 2022-04-04 10:30:36.468826406 +0100 BST m=+0.243571145 pod create c5bcd8e8d686c23611f7cc82a9eaf944c>

Apr 04 10:30:36 pi-vault podman[66167]: c5bcd8e8d686c23611f7cc82a9eaf944c3f4453f8fa2799072bef1e601ec5f23

Apr 04 10:30:37 pi-vault podman[66198]: 2022-04-04 10:30:37.066169857 +0100 BST m=+0.548978179 container init 918c4fc99ba15ee7e68a7dd66008d>

Apr 04 10:30:37 pi-vault podman[66198]: 2022-04-04 10:30:37.093123517 +0100 BST m=+0.575931859 container start 918c4fc99ba15ee7e68a7dd66008>

Apr 04 10:30:37 pi-vault podman[66198]: 2022-04-04 10:30:37.093861808 +0100 BST m=+0.576670149 pod start c5bcd8e8d686c23611f7cc82a9eaf944c3>

Apr 04 10:30:37 pi-vault podman[66198]: c5bcd8e8d686c23611f7cc82a9eaf944c3f4453f8fa2799072bef1e601ec5f23

Apr 04 10:30:37 pi-vault systemd[1]: Started Podman pod-photoprism.service.

Soma · 4. April 2022

Zitat von aldobranti

This is openmediavault-photoprism 6.0.1-3 on
Release: 6.0.20-1
OS is debian bullseye on RPi4b with 8Gb ram

Photoprism will not stay alive

# systemctl status pod-photoprism.service
● pod-photoprism.service - Podman pod-photoprism.service
Loaded: loaded (/etc/systemd/system/pod-photoprism.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-04-04 10:30:37 BST; 5s ago
Process: 66166 ExecStartPre=/bin/rm -f /run/pod-photoprism.pid /run/pod-photoprism.pod-id (code=exited, status=0/SUCCESS)
Process: 66167 ExecStartPre=/usr/bin/podman pod create --infra-conmon-pidfile /run/pod-photoprism.pid --pod-id-file /run/pod-photoprism>
Process: 66198 ExecStart=/usr/bin/podman pod start --pod-id-file /run/pod-photoprism.pod-id (code=exited, status=0/SUCCESS)
Main PID: 66305 (conmon)
Tasks: 2 (limit: 8985)
CPU: 768ms
CGroup: /system.slice/pod-photoprism.service
└─66305 /usr/bin/conmon --api-version 1 -c 918c4fc99ba15ee7e68a7dd66008d30e01359597a238019b50d9a90c327899ce -u 918c4fc99ba15ee>

Apr 04 10:30:36 pi-vault systemd[1]: Starting Podman pod-photoprism.service...
Apr 04 10:30:36 pi-vault podman[66167]: 2022-04-04 10:30:36.458569394 +0100 BST m=+0.233314132 container create 918c4fc99ba15ee7e68a7dd6600>
Apr 04 10:30:36 pi-vault podman[66167]: 2022-04-04 10:30:36.468826406 +0100 BST m=+0.243571145 pod create c5bcd8e8d686c23611f7cc82a9eaf944c>
Apr 04 10:30:36 pi-vault podman[66167]: c5bcd8e8d686c23611f7cc82a9eaf944c3f4453f8fa2799072bef1e601ec5f23
Apr 04 10:30:37 pi-vault podman[66198]: 2022-04-04 10:30:37.066169857 +0100 BST m=+0.548978179 container init 918c4fc99ba15ee7e68a7dd66008d>
Apr 04 10:30:37 pi-vault podman[66198]: 2022-04-04 10:30:37.093123517 +0100 BST m=+0.575931859 container start 918c4fc99ba15ee7e68a7dd66008>
Apr 04 10:30:37 pi-vault podman[66198]: 2022-04-04 10:30:37.093861808 +0100 BST m=+0.576670149 pod start c5bcd8e8d686c23611f7cc82a9eaf944c3>
Apr 04 10:30:37 pi-vault podman[66198]: c5bcd8e8d686c23611f7cc82a9eaf944c3f4453f8fa2799072bef1e601ec5f23
Apr 04 10:30:37 pi-vault systemd[1]: Started Podman pod-photoprism.service.

Alles anzeigen

Are you running arm64 version of RaspiOS?

If not, then it won't work.

aldobranti · 4. April 2022

the docker hub version of photoprism runs just fine on this platform under docker, seems like it is podman control that is giving me grief

Zoki · 4. April 2022

sudo podman ps -a

sudo podman logs <name_of_the_photo_prism_container_from_above_command>

Soma · 4. April 2022

Zitat von aldobranti

the docker hub version of photoprism runs just fine on this platform under docker, seems like it is podman control that is giving me grief

Even though docker version runs on armhf, it is still advised to use it on a 64Bit version.

Raspberry Pi - PhotoPrism

And this might not be the case with podman, hence the marking on the GUI that it runs on amd64 and arm64, NOT armhf.

So, if it works for you on docker, stick to it for the time beeing (those plugins are still beeing fine-tuned) or change your OS to arm64.

aldobranti · 4. April 2022

well all I know is

this box is

Linux pi-vault 5.15.30-v8+ #1536 SMP PREEMPT Mon Mar 28 13:53:14 BST 2022 aarch64 GNU/Linux

and

http://www.phoronix.com/scan.php?page=news_item&px=MTY5ODk

leads me to believe that aarch64 = arm64 && !( podman equivalent docker )

Soma · 4. April 2022

Yes, according to the uname -a, you're already running arm64.

But, as I said, the plugins are still beeing brushed and podman is not the same as docker.

Maybe try to clean the plugin, purge it and reinstall.

Zoki · 4. April 2022

Why don't you check the logs of the container?

aldobranti · 4. April 2022

I'd like to check the logs but the container has disappeared by the time I get to it -- may be a way to hang on to it -- all I have to go on otherwise is the systemctl status. I'm not so good with podman or docker for that matter

tsp001 · 4. April 2022

Zitat von votdev

Will be fixed in next version. In the meanwhile simply create the directory ...../proxy/data mentioned in the error message.

Thank you. Created the /proxy/data manually and was able to pass this issue now.

Now when I try to bring up the page with url 192.168.2.18:2342, I get page not found. How can I fix this?

votdev · 4. April 2022

Use different shared folder for the appdata folder. This will redeploy it from scratch. I think due the previous problems the database is ot of sync.

BTW, the new plugin package has been release, so the directory will be created automatically.

tsp001 · 5. April 2022

Zitat von votdev

Use different shared folder for the appdata folder. This will redeploy it from scratch. I think due the previous problems the database is ot of sync.

BTW, the new plugin package has been release, so the directory will be created automatically.

As suggested.

1. Did the latest update for plugin

2. Also, did the redeploy from scratch to new shared folder and It did create the required folder and db.

3. Now from the plugin, when I launch the GUI, i get "ERR_CONNECTION_TIMED_OUT".

Plugin page says this "Please note that the first deployment of the application can take a long time because the container images have to be downloaded first."

So, is something I am missing here or does this take a while to start working ?

This is what I see from podman ps --all command

Code

root@omv-nas:~# podman ps --all
CONTAINER ID  IMAGE                                   COMMAND               CREATED         STATUS             PORTS                   NAMES
0d3312f0a909  k8s.gcr.io/pause:3.2                                          21 minutes ago  Up 21 minutes ago  0.0.0.0:2342-&gt;2342/tcp  e04c1864c2fa-infra
5527af34576b  docker.io/mariadb:latest                mariadbd              21 minutes ago  Up 21 minutes ago  0.0.0.0:2342-&gt;2342/tcp  photoprism-db
2a577011b0d1  docker.io/library/caddy:latest          caddy run --confi...  21 minutes ago  Up 21 minutes ago  0.0.0.0:2342-&gt;2342/tcp  photoprism-proxy
c758e40c85fe  docker.io/photoprism/photoprism:latest  /opt/photoprism/b...  21 minutes ago  Up 21 minutes ago  0.0.0.0:2342-&gt;2342/tcp  photoprism-app

Code

root@omv-nas:~# podman logs --follow photoprism-db
2022-04-04 22:45:15+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.7.3+maria~focal started.
2022-04-04 22:45:15+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2022-04-04 22:45:15+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.7.3+maria~focal started.
2022-04-04 22:45:15+00:00 [Note] [Entrypoint]: Initializing database files
2022-04-04 22:45:16 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.


PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following command:

'/usr/bin/mysql_secure_installation'

which will also give you the option of removing the test
databases and anonymous user created by default.  This is
strongly recommended for production servers.

See the MariaDB Knowledgebase at https://mariadb.com/kb

Please report any problems at https://mariadb.org/jira

The latest information about MariaDB is available at https://mariadb.org/.

Consider joining MariaDB's strong and vibrant community:
https://mariadb.org/get-involved/

2022-04-04 22:45:33+00:00 [Note] [Entrypoint]: Database files initialized
2022-04-04 22:45:33+00:00 [Note] [Entrypoint]: Starting temporary server
2022-04-04 22:45:33+00:00 [Note] [Entrypoint]: Waiting for server startup
2022-04-04 22:45:33 0 [Note] mariadbd (server 10.7.3-MariaDB-1:10.7.3+maria~focal) starting as process 95 ...
2022-04-04 22:45:33 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-04-04 22:45:33 0 [Note] InnoDB: Number of transaction pools: 1
2022-04-04 22:45:33 0 [Note] InnoDB: Using generic crc32 instructions
2022-04-04 22:45:33 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2022-04-04 22:45:33 0 [Note] InnoDB: Using Linux native AIO
2022-04-04 22:45:33 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2022-04-04 22:45:33 0 [Note] InnoDB: Completed initialization of buffer pool
2022-04-04 22:45:33 0 [Note] InnoDB: 128 rollback segments are active.
2022-04-04 22:45:33 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-04-04 22:45:33 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-04-04 22:45:33 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-04-04 22:45:33 0 [Note] InnoDB: 10.7.3 started; log sequence number 42173; transaction id 14
2022-04-04 22:45:33 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-04-04 22:45:33 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2022-04-04 22:45:33 0 [Warning] 'user' entry 'root@photoprism' ignored in --skip-name-resolve mode.
2022-04-04 22:45:33 0 [Warning] 'proxies_priv' entry '@% root@photoprism' ignored in --skip-name-resolve mode.
2022-04-04 22:45:33 0 [Note] mariadbd: ready for connections.
Version: '10.7.3-MariaDB-1:10.7.3+maria~focal'  socket: '/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
2022-04-04 22:45:34+00:00 [Note] [Entrypoint]: Temporary server started.
Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/leapseconds' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/tzdata.zi' as time zone. Skipping it.
2022-04-04 22:45:39+00:00 [Note] [Entrypoint]: Securing system users (equivalent to running mysql_secure_installation)
2022-04-04 22:45:39+00:00 [Note] [Entrypoint]: Creating database photoprism
2022-04-04 22:45:39+00:00 [Note] [Entrypoint]: Creating user photoprism
2022-04-04 22:45:39+00:00 [Note] [Entrypoint]: Giving user photoprism access to schema photoprism

2022-04-04 22:45:39+00:00 [Note] [Entrypoint]: Stopping temporary server
2022-04-04 22:45:39 0 [Note] mariadbd (initiated by: root[root] @ localhost []): Normal shutdown
2022-04-04 22:45:39 0 [Note] InnoDB: FTS optimize thread exiting.
2022-04-04 22:45:39 0 [Note] InnoDB: Starting shutdown...
2022-04-04 22:45:39 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2022-04-04 22:45:39 0 [Note] InnoDB: Buffer pool(s) dump completed at 220404 22:45:39
2022-04-04 22:45:39 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2022-04-04 22:45:39 0 [Note] InnoDB: Shutdown completed; log sequence number 42185; transaction id 15
2022-04-04 22:45:40 0 [Note] mariadbd: Shutdown complete

2022-04-04 22:45:40+00:00 [Note] [Entrypoint]: Temporary server stopped

2022-04-04 22:45:40+00:00 [Note] [Entrypoint]: MariaDB init process done. Ready for start up.

2022-04-04 22:45:40 0 [Note] mariadbd (server 10.7.3-MariaDB-1:10.7.3+maria~focal) starting as process 1 ...
2022-04-04 22:45:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-04-04 22:45:40 0 [Note] InnoDB: Number of transaction pools: 1
2022-04-04 22:45:40 0 [Note] InnoDB: Using generic crc32 instructions
2022-04-04 22:45:40 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2022-04-04 22:45:40 0 [Note] InnoDB: Using Linux native AIO
2022-04-04 22:45:40 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2022-04-04 22:45:40 0 [Note] InnoDB: Completed initialization of buffer pool
2022-04-04 22:45:40 0 [Note] InnoDB: 128 rollback segments are active.
2022-04-04 22:45:40 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-04-04 22:45:40 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-04-04 22:45:40 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-04-04 22:45:40 0 [Note] InnoDB: 10.7.3 started; log sequence number 42185; transaction id 14
2022-04-04 22:45:40 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-04-04 22:45:40 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-04-04 22:45:40 0 [Note] InnoDB: Buffer pool(s) load completed at 220404 22:45:40
2022-04-04 22:45:40 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2022-04-04 22:45:40 0 [Note] Server socket created on IP: '0.0.0.0'.
2022-04-04 22:45:40 0 [Note] Server socket created on IP: '::'.
2022-04-04 22:45:40 0 [Note] mariadbd: ready for connections.
Version: '10.7.3-MariaDB-1:10.7.3+maria~focal'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution

Alles anzeigen

tsp001 · 5. April 2022

Zitat von votdev

Use different shared folder for the appdata folder. This will redeploy it from scratch. I think due the previous problems the database is ot of sync.

BTW, the new plugin package has been release, so the directory will be created automatically.

Looks like reboot did the trick. I am able to bring up the photoprism page. Thanks for your help.

viktor6 · 21. Januar 2023

I don't want to start photoprism

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color photoprism 2>&1' with exit code '1': raspberrypi:
----------
          ID: create_photoprism_appdata_storage_dir
    Function: file.directory
        Name: /srv/dev-disk-by-uuid-a92616e3-8db5-4989-9e55-258365a94fea/storage //storage/
      Result: True
     Comment: The directory /srv/dev-disk-by-uuid-a92616e3-8db5-4989-9e55-258365a94fea/storage //storage is in the correct state
     Started: 18:12:41.909817
    Duration: 36.23 ms
     Changes:
----------
          ID: create_photoprism_appdata_db_dir
    Function: file.directory
        Name: /srv/dev-disk-by-uuid-a92616e3-8db5-4989-9e55-258365a94fea/storage //db/
      Result: True
     Comment: The directory /srv/dev-disk-by-uuid-a92616e3-8db5-4989-9e55-258365a94fea/storage //db is in the correct state
     Started: 18:12:41.946821
    Duration: 6.479 ms
     Changes:
----------
          ID: create_photoprism_app_container_systemd_unit_file
    Function: file.managed
        Name: /etc/systemd/system/container-photoprism-app.service
      Result: True
     Comment: File /etc/systemd/system/container-photoprism-app.service is in the correct state
     Started: 18:12:41.954038
    Duration: 620.89 ms
     Changes:
----------
          ID: create_photoprism_db_container_systemd_unit_file
    Function: file.managed
        Name: /etc/systemd/system/container-photoprism-db.service
      Result: True
     Comment: File /etc/systemd/system/container-photoprism-db.service is in the correct state
     Started: 18:12:42.575640
    Duration: 224.881 ms
     Changes:
----------
          ID: create_photoprism_pod_systemd_unit_file
    Function: file.managed
        Name: /etc/systemd/system/pod-photoprism.service
      Result: True
     Comment: File /etc/systemd/system/pod-photoprism.service is in the correct state
     Started: 18:12:42.801582
    Duration: 69.303 ms
     Changes:
----------
          ID: photoprism_pull_app_image
    Function: cmd.run
        Name: podman pull docker.io/photoprism/photoprism:latest
      Result: False
     Comment: Command "podman pull docker.io/photoprism/photoprism:latest" run
     Started: 18:12:42.878207
    Duration: 659341.156 ms
     Changes:
              ----------
              pid:
                  12648
              retcode:
                  125
              stderr:
                  Trying to pull docker.io/photoprism/photoprism:latest...
                  Getting image source signatures
                  Copying blob sha256:674dcffbc11c7b53344754cbbf3a36779de2085ba9ac9759a6e64d710695931a
                  Copying blob sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1
                  Copying blob sha256:0509fae36eb0656f8bdb23f8ae64100d893bcea2563e97468d337e04d2d0410b
                  Copying blob sha256:56fbc98970ca9fcf2f1ef6f83516ed9a898aa39502805200da1fcf713314843a
                  Copying blob sha256:eb97349d77e1f92f40cc89cc8ba1b2e378d34ed7863be23387cc92b49e7e261b
                  Copying blob sha256:9aecf24919d065807aa2cdbf759c261bdf0f5699b051ec94cd04c63a5fbab25f
                  Copying blob sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1
                  Copying blob sha256:d608e68af9e95be234a5c713e2d52dd5eb80980984b0f4385bab3ec0a61f2607
                    write /var/tmp/storage372395167/4: no space left on device
                  Error: Error writing blob: error storing blob to file "/var/tmp/storage372395167/4": write /var/tmp/storage372395167/4: no space left on device
              stdout:

Summary for raspberrypi
------------
Succeeded: 5 (changed=1)
Failed:    1
------------
Total states run:     6
Total run time: 660.299 s

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color photoprism 2>&1' with exit code '1': raspberrypi:
----------
          ID: create_photoprism_appdata_storage_dir
    Function: file.directory
        Name: /srv/dev-disk-by-uuid-a92616e3-8db5-4989-9e55-258365a94fea/storage //storage/
      Result: True
     Comment: The directory /srv/dev-disk-by-uuid-a92616e3-8db5-4989-9e55-258365a94fea/storage //storage is in the correct state
     Started: 18:12:41.909817
    Duration: 36.23 ms
     Changes:
----------
          ID: create_photoprism_appdata_db_dir
    Function: file.directory
        Name: /srv/dev-disk-by-uuid-a92616e3-8db5-4989-9e55-258365a94fea/storage //db/
      Result: True
     Comment: The directory /srv/dev-disk-by-uuid-a92616e3-8db5-4989-9e55-258365a94fea/storage //db is in the correct state
     Started: 18:12:41.946821
    Duration: 6.479 ms
     Changes:
----------
          ID: create_photoprism_app_container_systemd_unit_file
    Function: file.managed
        Name: /etc/systemd/system/container-photoprism-app.service
      Result: True
     Comment: File /etc/systemd/system/container-photoprism-app.service is in the correct state
     Started: 18:12:41.954038
    Duration: 620.89 ms
     Changes:
----------
          ID: create_photoprism_db_container_systemd_unit_file
    Function: file.managed
        Name: /etc/systemd/system/container-photoprism-db.service
      Result: True
     Comment: File /etc/systemd/system/container-photoprism-db.service is in the correct state
     Started: 18:12:42.575640
    Duration: 224.881 ms
     Changes:
----------
          ID: create_photoprism_pod_systemd_unit_file
    Function: file.managed
        Name: /etc/systemd/system/pod-photoprism.service
      Result: True
     Comment: File /etc/systemd/system/pod-photoprism.service is in the correct state
     Started: 18:12:42.801582
    Duration: 69.303 ms
     Changes:
----------
          ID: photoprism_pull_app_image
    Function: cmd.run
        Name: podman pull docker.io/photoprism/photoprism:latest
      Result: False
     Comment: Command "podman pull docker.io/photoprism/photoprism:latest" run
     Started: 18:12:42.878207
    Duration: 659341.156 ms
     Changes:
              ----------
              pid:
                  12648
              retcode:
                  125
              stderr:
                  Trying to pull docker.io/photoprism/photoprism:latest...
                  Getting image source signatures
                  Copying blob sha256:674dcffbc11c7b53344754cbbf3a36779de2085ba9ac9759a6e64d710695931a
                  Copying blob sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1
                  Copying blob sha256:0509fae36eb0656f8bdb23f8ae64100d893bcea2563e97468d337e04d2d0410b
                  Copying blob sha256:56fbc98970ca9fcf2f1ef6f83516ed9a898aa39502805200da1fcf713314843a
                  Copying blob sha256:eb97349d77e1f92f40cc89cc8ba1b2e378d34ed7863be23387cc92b49e7e261b
                  Copying blob sha256:9aecf24919d065807aa2cdbf759c261bdf0f5699b051ec94cd04c63a5fbab25f
                  Copying blob sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1
                  Copying blob sha256:d608e68af9e95be234a5c713e2d52dd5eb80980984b0f4385bab3ec0a61f2607
                    write /var/tmp/storage372395167/4: no space left on device
                  Error: Error writing blob: error storing blob to file "/var/tmp/storage372395167/4": write /var/tmp/storage372395167/4: no space left on device
              stdout:

Summary for raspberrypi
------------
Succeeded: 5 (changed=1)
Failed:    1
------------
Total states run:     6
Total run time: 660.299 s in /usr/share/php/openmediavault/system/process.inc:220
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(170): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatus8G...', '/tmp/bgoutputGf...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(192): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Alles anzeigen

Soma · 21. Januar 2023

Zitat von viktor6

write /var/tmp/storage372395167/4: no space left on device Error: Error writing blob: error storing blob to file "/var/tmp/storage372395167/4": write /var/tmp/storage372395167/4: no space left on device

How much RAM you have?

What hardware you have?

viktor6 · 21. Januar 2023

Zitat von Soma

How much RAM you have?
What hardware you have?

RAM 1 g

hardware Raspberry pi 3+

ryecoaaron · 21. Januar 2023

Not enough ram or processing power on an RPi3 for photoprism.

PhotoPrism - Setup

Official Documentation

docs.photoprism.app

Unable to get Photoprism working

tsp001 5. April 2022

Jetzt mitmachen!

Tags