Can you check in the program_files directory and see if there is a temp.txt file? If there is, first delete that. Next, run Update m3u(s) and XML EPG(s). If it is still going after 6-7 minutes, get me the latest logs in this range:
2024-11-19 11:30:00.181504: Starting generation of final m3u(s) and XML EPG(s)...
Deleted: plm_epg_hls_m3u_01.m3u
Deleted: plm_gracenote_hls_m3u_01.m3u
Deleted: plm_gracenote_mpeg_ts_m3u_01.m3u
Created: plm_gracenote_hls_m3u_01.m3u
Created: plm_gracenote_mpeg_ts_m3u_01.m3u
Created: plm_epg_hls_m3u_01.m3u
[DEBUG | 2024-11-19 11:30:03,648] - Starting new HTTP connection (1): localhost:7971
[DEBUG | 2024-11-19 11:30:03,973] - http://localhost:7971 "GET /plex/epg/local/epg-local.xml HTTP/1.1" 200 44467404
[DEBUG | 2024-11-19 11:30:05,996] - Starting new HTTP connection (1): localhost:7972
[DEBUG | 2024-11-19 11:30:06,261] - http://localhost:7972 "GET /pluto/epg/local/epg-local.xml HTTP/1.1" 200 12794658
[DEBUG | 2024-11-19 11:30:06,777] - Starting new HTTP connection (1): localhost:7977
[DEBUG | 2024-11-19 11:30:07,622] - http://localhost:7977 "GET /epg.xml?regions=us HTTP/1.1" 200 None
[DEBUG | 2024-11-19 11:30:07,988] - Encoding detection: utf_8 is most likely the one.
[DEBUG | 2024-11-19 11:30:08,004] - Starting new HTTP connection (1): localhost:7970
[DEBUG | 2024-11-19 11:30:48,440] - http://localhost:7970 "GET /tubi/epg.xml HTTP/1.1" 200 3311346
[DEBUG | 2024-11-19 11:30:48,512] - Starting new HTTP connection (1): localhost:7973
[DEBUG | 2024-11-19 11:30:52,021] - http://localhost:7973 "GET /distrotv/epg.xml HTTP/1.1" 200 889012
Deleted: plm_epg_hls_m3u_01.xml
Created: plm_epg_hls_m3u_01.xml
2024-11-19 11:32:19.907704: Finished generation of final m3u(s) and XML EPG(s).
It it completes this time, check to see if that temp.txt file is there. It it is, it looks like there might be some Mac security issue I need to attend to.
My thought is this: the way PLM works with the XML is it reads all the XML guides and copies their contents into a new temp.txt files. Then it reads that file and matches up against the stations in the EPG m3u(s), creating the corresponding XML files. After that, it deletes the temp.txt file. If security is not allowing the temp.txt to be deleted, then the file will just keep getting bigger and bigger, meaning it will take even longer to read it. By my calculation (182 stations in 87 seconds from the log above), mine is taking about a bit less than half a second per station to read the temp.txt file and write it the output XML file, so your 666 stations should take about five and half minutes, hence why I asked you to check in after 6-7 minutes total.