Core.* files ?

[ceejayemm]

NextPVR: 7.1.1.260616

I have been running various versions of NextPVR in a Docker container for a while and yesterday added a new disk to my existing installation to give me some additional recording space .  I restarted the docker container and all seemed well. Just for completeness I had a look around the various persistent storage locations to see that things were appearing where I thought they should be.  My Docker Compose file looks like:

Code:

services:
  nextpvr:
    image: nextpvr/nextpvr_amd64:stable
    container_name: nextpvr
    ports:
      - 16891:16891/udp
      - 8866:8866
    volumes:
      - /mnt/disk1/npvr/config:/config
      - /mnt/disk1/npvr/local:/local
      - /mnt/disk1/npvr/buffer:/buffer
#      - /nfs/recordings:/recordings     
      - /etc/localtime:/etc/localtime:ro
    devices:
      - /dev/dri:/dev/dri
    environment:
      - TZ=Europe/London
      - PUID=1000
      - PGID=100
    restart: unless-stopped

The 'recordings' is disabled by choice, all my recordings are saved to folders within the 'local' folder for later post-processing, which is working fine.

Checking the Config folder (/mnt/disk1/npvr/config) I seem to have a load (currently 24) files named core.nnnnnn where nnnnnn is variable number between 876 and 115076 all dated between 17:55 and 17:56 yesterday which is when i restarted the container.

Code:

ceejayemm@cmdock-av1:/mnt/disk1/npvr/config/scripts$ ls -la
total 4383484
drwxr-xr-x 3 root root       4096 Jul  2 10:07 .
drwxr-xr-x 7 root root       4096 Jul  2 04:06 ..
-rwxr-xr-x 1 root root       5421 Jul  1 17:55 comskip.ini
-rw------- 1 root root 2557796352 Jul  1 17:56 core.1028
-rw------- 1 root root 2557480960 Jul  1 17:55 core.11426
-rw------- 1 root root 2558160896 Jul  1 17:55 core.115076
-rw------- 1 root root 2557804544 Jul  1 17:55 core.11874
-rw------- 1 root root 2557104128 Jul  1 17:55 core.18874
-rw------- 1 root root 2557927424 Jul  1 17:55 core.30266
-rw------- 1 root root 2558377984 Jul  1 17:55 core.30756
-rw------- 1 root root 2559025152 Jul  1 17:56 core.30899
-rw------- 1 root root 2564562944 Jul  1 17:56 core.30911
-rw------- 1 root root 2547126272 Jul  1 17:56 core.31172
-rw------- 1 root root 2556534784 Jul  1 17:55 core.34902
-rw------- 1 root root 2557116416 Jul  1 17:56 core.35873
-rw------- 1 root root 2557747200 Jul  1 17:55 core.36018
-rw------- 1 root root 2557292544 Jul  1 17:55 core.36165
-rw------- 1 root root 2557063168 Jul  1 17:55 core.38399
-rw------- 1 root root 2558607360 Jul  1 17:55 core.42037
-rw------- 1 root root 2557673472 Jul  1 17:55 core.46229
-rw------- 1 root root 2556063744 Jul  1 17:55 core.47932
-rw------- 1 root root 2556477440 Jul  1 17:55 core.5048
-rw------- 1 root root 2558099456 Jul  1 17:55 core.87275
-rw------- 1 root root 2558562304 Jul  1 17:56 core.876
-rw------- 1 root root 2558009344 Jul  1 17:55 core.88003
-rw------- 1 root root 2558488576 Jul  1 17:56 core.905
-rw------- 1 root root 2556547072 Jul  1 17:56 core.917
drwxr-xr-x 2 root root       4096 Jul  1 17:55 logs
-rwxr-xr-x 1 root root       1473 Jul  2 09:59 NextPVR_Copies.sh
-rwxr-xr-x 1 root root       2646 Jul  1 17:55 PostProcessing.sh
-rwxr-xr-x 1 root root        111 Jul  1 17:55 PostUpdateEPG.sh
-rwxr-xr-x 1 root root        557 Jul  2 09:56 recordings_tidy.sh

NextPVR seems to be running correctly with no other issues I am aware of.  What might be creating these files and can I get rid of them ?  This might have been happening for a while, I just haven't seen these files before now.

Latest logs attached.

Chris

[mvallevand]

Your system crashed at that time and perhaps you have your Docker set to autorestart and it kept crashing until whatever caused it recovered.

It looks like you shutdown the Docker here

2026-07-01 17:17:05.811 [DEBUG][1] No /config/scripts/PreShutdown.sh

After the crashing instance the startup worked at

2026-07-01 18:09:25.938 [INFO][1] See LICENSE.txt for license information so maybe investigation what

So maybe try and figure out what you were doing to your environment in that hour.

Your PostPorcessing file is bad too so you should probably fix that while you are looking

Martin

[ceejayemm]

Martin

Thanks for looking at this for me. The hour between 17:00 and 18:00 yesterday is roughly when I had the server shutdown to install the new disk. It was recording something shortly before I closed it down, maybe it hadn't finished what it was doing after the recording and picked up again on this when I first restarted the container? It seems I restarted the server initially at 17:42:26.372 (nrecord.log.2) which reported a lot of HDHR device errors and then a bit later, at 17:43:27.539, a Schedules Direct invalid login. My HDHR devices were available and my SD login details haven't changed. I must have realised I needed to make another change as I then shutdown again at 17:43:30.056 before restarting it again at 18:09:25.938 (nrecord.log.1). So it would seem that my server / container was shutdown at the time the core.* files were created (17:55 / 17:56).

I have corrected the PostProcessing.sh file (thanks for pointing this out - I hadn't noticed), deleted the core.* files and restarted the container this afternoon. So far the core.* files have not reappeared. Unless you can think of anything else, I will chalk this up to experience and close the ticket. I will keep an eye out to see if the core.* files reappear in future.

Thanks

Chris