Re: UMS closes by itself
Posted: Fri Feb 07, 2025 3:18 am
This link has the information and install files.
https://www.java.com/en/download/help/w ... nload.html
https://www.java.com/en/download/help/w ... nload.html
Universal Media Server | Forum
A short text to describe your forum
https://www.universalmediaserver.com/forum/
UMS closes by itself
https://www.universalmediaserver.com/forum/viewtopic.php?t=16195
Page 3 of 4
Re: UMS closes by itself
Posted: Fri Feb 07, 2025 4:44 am
Many thanks, appreciate! I've just installed the last version and restarted UMS, let's see ...
Re: UMS closes by itself
Posted: Fri Feb 07, 2025 6:52 am
Unfortunately it didn't help as well. Attached please find new trace logs, I can't find anything suspecting ... Any idea?
P.S. I could just reproduce the following scenario, 100%! I go to my computer where UMS is installed via RDP (!) and start the UMS, afterwards I call the "old" settings panel to be sure that it's running. Now I close the RDP and start it again => UMS is down!! If I don't start that old settings panel, I can close the RDP and open it again and again - the UMS is still running! Is it perhaps just the issue with these old settings panel? Take into consideration that the screen resolution (and scaling) might be adjusted when RDP connects to the remote computer. I will observe this behaviour furthermore ...
P.P.S No, after about 20 min the UMS was down without that panel running on screen
P.S. I could just reproduce the following scenario, 100%! I go to my computer where UMS is installed via RDP (!) and start the UMS, afterwards I call the "old" settings panel to be sure that it's running. Now I close the RDP and start it again => UMS is down!! If I don't start that old settings panel, I can close the RDP and open it again and again - the UMS is still running! Is it perhaps just the issue with these old settings panel? Take into consideration that the screen resolution (and scaling) might be adjusted when RDP connects to the remote computer. I will observe this behaviour furthermore ...
P.P.S No, after about 20 min the UMS was down without that panel running on screen
Re: UMS closes by itself
Posted: Fri Feb 07, 2025 12:45 pm
The last log file was when UMS was in "WARN" mode and not "TRACE" mode so the information in that log file is limited.
You do have a huge amount of media files and I don't know if UMS has any limitation in that regard.
That said, I am pretty much out of ideas.
Perhaps mik_s or SubJunk could be of more help.
The only other things I could suggest (in order to try) are:
Stop UMS
Delete your database folder. Located at "C:\ProgramData\UMS\database"
Start UMS and the database folder will be recreated.
I still think it would be worthwhile doing what I said previously. This would tell us if the issue is with the media
files (too many or some other issue) or the issue is something else not to do with your media content.
Create a folder on your D: (call it Test).
Create 3 subfolders: Video Music Images
Copy 50 or so files to those subfolders. Make sure they are files with no strange characters in the name.
Modify your SHARED.conf
Add:
Then modify all the other entries in SHARED.conf for these settings to:
And one last thing to try.
In your "UMS.conf" located at: C:\ProgramData\UMS\UMS.conf
there are 2 settings:
The default for these is "true". These 2 settings use a lot of resources.
You could set them to false as a test and check if it makes any difference.
You do have a huge amount of media files and I don't know if UMS has any limitation in that regard.
That said, I am pretty much out of ideas.
Perhaps mik_s or SubJunk could be of more help.
The only other things I could suggest (in order to try) are:
Stop UMS
Delete your database folder. Located at "C:\ProgramData\UMS\database"
Start UMS and the database folder will be recreated.
I still think it would be worthwhile doing what I said previously. This would tell us if the issue is with the media
files (too many or some other issue) or the issue is something else not to do with your media content.
Create a folder on your D: (call it Test).
Create 3 subfolders: Video Music Images
Copy 50 or so files to those subfolders. Make sure they are files with no strange characters in the name.
Modify your SHARED.conf
Add:
Code: Select all
{
"file": "D:\\Test",
"monitored": true,
"metadata": true,
"active": true,
"groups": [],
"type": "Folder"
}Code: Select all
monitored": false,
"metadata": false,
"active": false,In your "UMS.conf" located at: C:\ProgramData\UMS\UMS.conf
there are 2 settings:
Code: Select all
generate_thumbnails =
image_thumbnails =You could set them to false as a test and check if it makes any difference.
Code: Select all
generate_thumbnails = false
image_thumbnails = falseRe: UMS closes by itself
Posted: Sun Feb 09, 2025 10:00 pm
Thanks for this hint! I set thumbnails to false and the UMS is running w/o crash so far. Kind of workaround, but ok for me.boss wrote: ↑Fri Feb 07, 2025 12:45 pm And one last thing to try.
In your "UMS.conf" located at: C:\ProgramData\UMS\UMS.conf
there are 2 settings:
generate_thumbnails =
image_thumbnails =
The default for these is "true". These 2 settings use a lot of resources.
You could set them to false as a test and check if it makes any difference.
generate_thumbnails = false
image_thumbnails = false
Re: UMS closes by itself
Posted: Mon Feb 10, 2025 12:13 am
I actually have both of those settings set to "false" on my setup.
You do have a huge amount of media files and hopefully having those settings set to "false" will greatly reduce the resources being used by your computer and solve your issue,
Cheers
You do have a huge amount of media files and hopefully having those settings set to "false" will greatly reduce the resources being used by your computer and solve your issue,
Cheers
Re: UMS closes by itself
Posted: Mon Feb 10, 2025 3:52 am
I'm kinda back to being able to analyse log files but have to set things up from scratch so not back to where I was.
I looked at the original logs and there are a lot of memory heap problems.
Interestingly whenever this happens there are multiple writes to GUI.conf which I had not not paid any attention to before so did not know what it does.
I found that it is the position of the old GUI when you move or resize the window so if you are only using the web UI this should not be changing.
Testing on mine moving the window once produces this entry 11 times so it is either repeating the message for some reason or it is actually writing 11 times each change.
In the newer debug.log.prev.zip log you posted it is trying to write to this conf but the window must not be open
The logs were not in TRACE mode so I could not see any more information
@boss the filenames are correct. If you change the text encoding in your text editor to UTF-8 it will display correctly like
I use this for viewing logs and I have to change the encoding to display non ASCII correctly.
(I should have updated that post with my all in one filters that I was using)
There may be a problem with cyrillic characters or the windows name shortening as it is breaking some things like recognising image format,
And this is what mainly shows in debug.0005.zip
dcrawMS for RAW image files where the command is malformed with ??????'s
As well as MP3s
This does not happen with every file though.
I don't know if this is linked to the memory problems.
I noticed that the names in a playlist is not displaying correctly, at least in the logs, so don't know if this is another issue.
@yawa It is better to only share the media folders on your drives and not the whole drive itself if there are other things on it as it will slow down scanning.
It would be better to set up seperate Image, Video, and Music folders and will be quicker to access on your device while browsing.
No need to edit the SHARED.conf youself though, it is easier to do with the web UI.
setting "active: false" means this folder will be disabled and "monitored: false" means UMS will not track played status or when new files are added to this folder.
Normally you would want these to be true but disabling all but a folder with a small number of files will be good for testing.
Turning off thumbnails will help with resources while scanning but once they are generated they will be stored in the database so should not have an impact after that.
Maybe becasue of the number of files in your library the database is too large. This can also somtimes happen after an update if the database is not upgraded properly and can bloat the database.
You could try uninstalling UMS and do a clean install of the latest version with all the settings at default and only add a few shared folders including some of the problem ones that have showed as errors I posted above.
Also edit UMS.conf while it is not running to add
so any errors and the cause will be capured in the logs with as much detail possible if it shuts down again.
UMS comes with the Java runtime files so you don't need to install Java.
There were issues with this in the past when it used the system Java that may be an old or incompatble version. It can still be a problem on Linux though.
If you did want to run another version of Java you would also need to edit UMS.conf for the path to that installation.
No need to use RDP (I assume you mean remote desktop) to check on UMS on another computer.
Just use the IP address of that computer in the web browser like http://192.168.178.163:5001 (I think this the right IP of the computer running UMS for you)
@boss Thanks a lot for helping when I had computer problems.
I looked at the original logs and there are a lot of memory heap problems.
Code: Select all
[AWT-EventQueue-0] net.pms.util.SystemErrWrapper Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap spaceCode: Select all
[AWT-EventQueue-0] net.pms.util.SystemErrWrapper Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap space
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[NetworkConfiguration Watcher] net.pms.network.configuration.NetworkConfiguration Checking network configuration changes
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[NetworkConfiguration Watcher] net.pms.network.configuration.NetworkConfiguration Checking network configuration changes
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[NetworkConfiguration Watcher] net.pms.network.configuration.NetworkConfiguration Checking network configuration changes
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[NetworkConfiguration Watcher] net.pms.network.configuration.NetworkConfiguration Checking network configuration changes
[AWT-EventQueue-0] net.pms.configuration.GuiConfiguration Writing window configuration file: C:\ProgramData\UMS\GUI.conf
[AWT-EventQueue-0] net.pms.util.SystemErrWrapper Exception in thread "AWT-EventQueue-0" java.lang.OutOfMemoryError: Java heap spaceTesting on mine moving the window once produces this entry 11 times so it is either repeating the message for some reason or it is actually writing 11 times each change.
In the newer debug.log.prev.zip log you posted it is trying to write to this conf but the window must not be open
Code: Select all
DEBUG 2025-02-06 12:14:12.793 [Media Scanner] Scanning folder: 1995 - Satoru Oda & Hank Jones Great Jazz Quintet - Just Friends
DEBUG 2025-02-06 12:14:14.951 [AWT-EventQueue-0] Writing window configuration file: C:\ProgramData\UMS\GUI.conf
INFO 2025-02-06 12:14:15.158 [AWT-EventQueue-0] Exception in thread "AWT-EventQueue-0" java.awt.AWTError: no screen devices
INFO 2025-02-06 12:14:15.159 [AWT-EventQueue-0] at java.desktop/sun.awt.Win32GraphicsEnvironment.getDefaultScreenDevice(Unknown Source)
INFO 2025-02-06 12:14:15.159 [AWT-EventQueue-0] at java.desktop/sun.awt.windows.WWindowPeer.updateGC(Unknown Source)
INFO 2025-02-06 12:14:15.197 [AWT-EventQueue-0] at java.desktop/java.awt.event.InvocationEvent.dispatch(Unknown Source)
INFO 2025-02-06 12:14:15.197 [AWT-EventQueue-0] at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source)
INFO 2025-02-06 12:14:15.197 [AWT-EventQueue-0] at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
INFO 2025-02-06 12:14:15.197 [AWT-EventQueue-0] at java.desktop/java.awt.EventQueue$4.run(Unknown Source)
INFO 2025-02-06 12:14:15.197 [AWT-EventQueue-0] at java.base/java.security.AccessController.doPrivileged(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.desktop/java.awt.EventQueue$5.run(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.desktop/java.awt.EventQueue$5.run(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.base/java.security.AccessController.doPrivileged(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
INFO 2025-02-06 12:14:15.199 [AWT-EventQueue-0] at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
INFO 2025-02-06 12:14:15.207 [AWT-EventQueue-0] at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source)
INFO 2025-02-06 12:14:15.208 [AWT-EventQueue-0] at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)
@boss the filenames are correct. If you change the text encoding in your text editor to UTF-8 it will display correctly like
Code: Select all
D:\Photos\2024 Фотоархив\03\Гриша Читакль март\PXL_20240315_095101312.jpg(I should have updated that post with my all in one filters that I was using)
There may be a problem with cyrillic characters or the windows name shortening as it is breaking some things like recognising image format,
Code: Select all
Using short path name of "D:\Photos\2024 Фотоархив\03\Гриша Читакль март\PXL_20240315_095101312.jpg": "D:\Photos\2024 Фотоархив\03\Гриша Читакль март\PXL_20240315_095101312.jpg"
Matched format JPG to "D:\Photos\2024 Фотоархив\03\Гриша Читакль март\PXL_20240315_095101312.jpg"
Store does not yet contain MediaInfo for D:\Photos\2024 Фотоархив\03\Гриша Читакль март\PXL_20240315_095101312.jpg
Send event "SystemUpdateID" update from 499202 to 499203
Parsing image file "D:\Photos\2024 Фотоархив\03\Гриша Читакль март\PXL_20240315_095101312.jpg"
Image parsing for "D:\Photos\2024 Фотоархив\03\Гриша Читакль март\PXL_20240315_095101312.jpg" failed both with MediaInfo and internally: Unable to recognize image format for "D:\Photos\2024 Фотоархив\03\Гриша Читакль март\PXL_20240315_095101312.jpg" - parsing failed
net.pms.util.UnknownFormatException: Unable to recognize image format for "D:\Photos\2024 Фотоархив\03\Гриша Читакль март\PXL_20240315_095101312.jpg" - parsing failed
at net.pms.parsers.MetadataExtractorParser.parseStream(MetadataExtractorParser.java:212)
at net.pms.parsers.MetadataExtractorParser.parse(MetadataExtractorParser.java:135)
at net.pms.parsers.MediaInfoParser.parse(MediaInfoParser.java:456)
at net.pms.parsers.Parser.parse(Parser.java:79)
at net.pms.store.MediaInfoStore.getMediaInfo(MediaInfoStore.java:152)
at net.pms.store.item.RealFile.resolve(RealFile.java:249)
at net.pms.store.StoreItem.syncResolve(StoreItem.java:1464)
at net.pms.store.item.RealFile.syncResolve(RealFile.java:328)
at net.pms.store.StoreResource.run(StoreResource.java:308)
at net.pms.store.item.RealFile.isValid(RealFile.java:125)
at net.pms.store.StoreContainer.addChildItem(StoreContainer.java:131)
at net.pms.store.StoreContainer.addChild(StoreContainer.java:122)
at net.pms.store.container.VirtualFolder.manageFile(VirtualFolder.java:115)
at net.pms.store.container.VirtualFolder.analyzeChildren(VirtualFolder.java:198)
at net.pms.store.container.VirtualFolder.discoverChildren(VirtualFolder.java:323)
at net.pms.store.MediaScanner.scan(MediaScanner.java:141)
at net.pms.store.MediaScanner.scan(MediaScanner.java:147)
at net.pms.store.MediaScanner.scan(MediaScanner.java:147)
at net.pms.store.MediaScanner.scan(MediaScanner.java:147)
at net.pms.store.MediaScanner.scan(MediaScanner.java:147)
at net.pms.store.MediaScanner.startScan(MediaScanner.java:98)
at net.pms.store.MediaScanner.lambda$startMediaScan$0(MediaScanner.java:198)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: net.pms.util.UnknownFormatException: Unable to find a suitable image reader
at net.pms.parsers.MetadataExtractorParser.readImageInfo(MetadataExtractorParser.java:856)
at net.pms.parsers.MetadataExtractorParser.parseStream(MetadataExtractorParser.java:209)
... 22 common frames omitted
dcrawMS for RAW image files where the command is malformed with ??????'s
Code: Select all
Using short path name of "D:\Photos\2022 Фотоархив\2022 03 20 Демо война Landtag\DSC_4161.NEF": "D:\Photos\2022 Фотоархив\2022 03 20 Демо война Landtag\DSC_4161.NEF"
Matched format RAW to "D:\Photos\2022 Фотоархив\2022 03 20 Демо война Landtag\DSC_4161.NEF"
Store does not yet contain MediaInfo for D:\Photos\2022 Фотоархив\2022 03 20 Демо война Landtag\DSC_4161.NEF
Parsing RAW image "DSC_4161.NEF" with DCRaw
Starting "C:\Program Files\Universal Media Server\bin\dcrawMS.exe" -i -v "D:\Photos\2022 Фотоархив\2022 03 20 Демо война Landtag\DSC_4161.NEF"
Send event "SystemUpdateID" update from 449790 to 449792
Process ID (C:\Program Files\Universal Media Server\bin\dcrawMS.exe): 10224
D:\Photos\2022 ?????????\2022 03 20 ???? ????? Landtag\DSC_4161.NEF: Invalid argument
Process C:\Program Files\Universal Media Server\bin\dcrawMS.exe has a return code of 1! Maybe an error occurred... check the log file
Parsing image file "D:\Photos\2022 Фотоархив\2022 03 20 Демо война Landtag\DSC_4161.NEF"
Unable to parse "D:\Photos\2022 Фотоархив\2022 03 20 Демо война Landtag\DSC_4161.NEF" with ImageIO because the format is unsupported, image information will be limited
ImageIO parse failure reason: Unable to find a suitable image reader
Parsing of image "D:\Photos\2022 Фотоархив\2022 03 20 Демо война Landtag\DSC_4161.NEF" completed
Unhandled exception while resolving DSC_4161: For input string: "4F4"
java.lang.NumberFormatException: For input string: "4F4"
at java.base/java.lang.NumberFormatException.forInputString(Unknown Source)
at java.base/java.lang.Long.parseLong(Unknown Source)
at java.base/java.lang.Long.valueOf(Unknown Source)
at net.pms.parsers.MediaInfoParser.getSpecificID(MediaInfoParser.java:1090)
at net.pms.parsers.MediaInfoParser.parse(MediaInfoParser.java:505)
at net.pms.parsers.Parser.parse(Parser.java:79)
at net.pms.store.MediaInfoStore.getMediaInfo(MediaInfoStore.java:152)
at net.pms.store.item.RealFile.resolve(RealFile.java:249)
at net.pms.store.StoreItem.syncResolve(StoreItem.java:1464)
at net.pms.store.item.RealFile.syncResolve(RealFile.java:328)
at net.pms.store.StoreResource.run(StoreResource.java:308)
at net.pms.store.item.RealFile.isValid(RealFile.java:125)
at net.pms.store.StoreContainer.addChildItem(StoreContainer.java:131)
at net.pms.store.StoreContainer.addChild(StoreContainer.java:122)
at net.pms.store.container.VirtualFolder.manageFile(VirtualFolder.java:115)
at net.pms.store.container.VirtualFolder.analyzeChildren(VirtualFolder.java:198)
at net.pms.store.container.VirtualFolder.discoverChildren(VirtualFolder.java:323)
at net.pms.store.MediaScanner.scan(MediaScanner.java:141)
at net.pms.store.MediaScanner.scan(MediaScanner.java:147)
at net.pms.store.MediaScanner.scan(MediaScanner.java:147)
at net.pms.store.MediaScanner.scan(MediaScanner.java:147)
at net.pms.store.MediaScanner.startScan(MediaScanner.java:98)
at net.pms.store.MediaScanner.lambda$startMediaScan$0(MediaScanner.java:198)
at java.base/java.lang.Thread.run(Unknown Source)
Code: Select all
TRACE 2025-02-01 21:19:59.587 [Media Scanner] net.pms.platform.windows.WindowsUtils Using short path name of "D:\Audiobooks\Стругацкие А. и Б. - Хромая судьба (Владимир Левашев)\04\04_25.mp3": "D:\Audiobooks\Стругацкие А. и Б. - Хромая судьба (Владимир Левашев)\04\04_25.mp3"
TRACE 2025-02-01 21:19:59.587 [Media Scanner] net.pms.formats.FormatFactory Matched format MP3 to "D:\Audiobooks\Стругацкие А. и Б. - Хромая судьба (Владимир Левашев)\04\04_25.mp3"
TRACE 2025-02-01 21:19:59.587 [Media Scanner] net.pms.store.MediaInfoStore Store does not yet contain MediaInfo for D:\Audiobooks\Стругацкие А. и Б. - Хромая судьба (Владимир Левашев)\04\04_25.mp3
TRACE 2025-02-01 21:19:59.587 [Media Scanner] net.pms.database.MediaTableAudioMetadata Searching AUDIO_METADATA with "HikariProxyPreparedStatement@1621148338 wrapping prep43083: SELECT * FROM AUDIO_METADATA WHERE FILEID = ? LIMIT 1 {1: CAST(7720 AS BIGINT)}"
TRACE 2025-02-01 21:19:59.587 [Media Scanner] net.pms.database.MediaTableVideoMetadata Searching VIDEO_METADATA with "HikariProxyPreparedStatement@450091440 wrapping prep43084: SELECT * FROM VIDEO_METADATA WHERE VIDEO_METADATA.FILEID = ? AND (VIDEO_METADATA.IMDBID IS NOT NULL OR VIDEO_METADATA.TMDBID IS NOT NULL) LIMIT 1 {1: CAST(7720 AS BIGINT)}"
DEBUG 2025-02-01 21:19:59.732 [Media Scanner] net.pms.parsers.JaudiotaggerParser Error parsing audio file tag for "04_25.mp3": No audio header found within 04_25.mp3
TRACE 2025-02-01 21:19:59.732 [Media Scanner] net.pms.parsers.JaudiotaggerParser
org.jaudiotagger.audio.exceptions.InvalidAudioFrameException: No audio header found within 04_25.mp3
at org.jaudiotagger.audio.mp3.MP3AudioHeader.<init>(MP3AudioHeader.java:146)
at org.jaudiotagger.audio.mp3.MP3File.<init>(MP3File.java:387)
at org.jaudiotagger.audio.mp3.MP3FileReader.read(MP3FileReader.java:39)
at org.jaudiotagger.audio.AudioFileIO.readFile(AudioFileIO.java:356)
at org.jaudiotagger.audio.AudioFileIO.read(AudioFileIO.java:192)
at net.pms.parsers.JaudiotaggerParser.parse(JaudiotaggerParser.java:79)
at net.pms.parsers.FFmpegParser.parse(FFmpegParser.java:83)
at net.pms.store.item.RealFile.isValid(RealFile.java:141)
at net.pms.store.StoreContainer.addChildItem(StoreContainer.java:131)
at net.pms.store.StoreContainer.addChild(StoreContainer.java:122)
at net.pms.store.container.VirtualFolder.manageFile(VirtualFolder.java:115)
at net.pms.store.container.VirtualFolder.analyzeChildren(VirtualFolder.java:198)
at net.pms.store.container.VirtualFolder.discoverChildren(VirtualFolder.java:323)
at net.pms.store.MediaScanner.scan(MediaScanner.java:141)
at net.pms.store.MediaScanner.scan(MediaScanner.java:147)
at net.pms.store.MediaScanner.scan(MediaScanner.java:147)
at net.pms.store.MediaScanner.scan(MediaScanner.java:147)
at net.pms.store.MediaScanner.startScan(MediaScanner.java:98)
at net.pms.store.MediaScanner.lambda$startMediaScan$0(MediaScanner.java:198)
at java.base/java.lang.Thread.run(Unknown Source)
INFO 2025-02-01 21:19:59.736 [Media Scanner] net.pms.store.item.RealFile The file D:\Audiobooks\Стругацкие А. и Б. - Хромая судьба (Владимир Левашев)\04\04_25.mp3 could not be parsed. It will be hidden
I don't know if this is linked to the memory problems.
I noticed that the names in a playlist is not displaying correctly, at least in the logs, so don't know if this is another issue.
Code: Select all
DEBUG 2025-02-06 12:08:46.949 [Media Scanner] Scanning folder: bday
DEBUG 2025-02-06 12:08:47.510 [Media Scanner] Reading m3u playlist: play.m3u
DEBUG 2025-02-06 12:08:47.510 [Media Scanner] Adding playlist entry: [01.mp3,Ìàøèíà âðåìåíè - Âîò ÷òî ñòðàííî]
DEBUG 2025-02-06 12:08:47.512 [Media Scanner] Adding playlist entry: [02.mp3,Ìàøèíà âðåìåíè - Ñêàæåì ïðÿìî]
DEBUG 2025-02-06 12:08:47.521 [Media Scanner] Adding playlist entry: [03.mp3,Ìàøèíà âðåìåíè - Äåíü ðîæäåíüÿ]
...
@yawa It is better to only share the media folders on your drives and not the whole drive itself if there are other things on it as it will slow down scanning.
It would be better to set up seperate Image, Video, and Music folders and will be quicker to access on your device while browsing.
No need to edit the SHARED.conf youself though, it is easier to do with the web UI.
- Clipboard Image (1).jpg (43.88 KiB) Viewed 16799 times
Normally you would want these to be true but disabling all but a folder with a small number of files will be good for testing.
Turning off thumbnails will help with resources while scanning but once they are generated they will be stored in the database so should not have an impact after that.
Maybe becasue of the number of files in your library the database is too large. This can also somtimes happen after an update if the database is not upgraded properly and can bloat the database.
You could try uninstalling UMS and do a clean install of the latest version with all the settings at default and only add a few shared folders including some of the problem ones that have showed as errors I posted above.
Also edit UMS.conf while it is not running to add
Code: Select all
log_level = TRACEUMS comes with the Java runtime files so you don't need to install Java.
There were issues with this in the past when it used the system Java that may be an old or incompatble version. It can still be a problem on Linux though.
If you did want to run another version of Java you would also need to edit UMS.conf for the path to that installation.
No need to use RDP (I assume you mean remote desktop) to check on UMS on another computer.
Just use the IP address of that computer in the web browser like http://192.168.178.163:5001 (I think this the right IP of the computer running UMS for you)
@boss Thanks a lot for helping when I had computer problems.
Re: UMS closes by itself
Posted: Mon Feb 10, 2025 11:56 pm
Hey, @mik_s, awesome, many thanks for your feedback and investigations! I've already adjusted the list of the shared folders, it looks like this atm (pls find screenshot attached). This didn't help though, I had crashes afterwards. Just after I set thumbnails to false the UNS was running smoothly, still running since several days w/o any crash. And well, I should be careful with the old GUI interface, although it offers much more settings to be configured, obviously it has some issues leading to crash (100% reproducable).
And yes, my DB is pretty large, actually about 620 Mb.
Ok, I will set the TRACE mode as suggested next time if UMS will have an issue. Thank you!
Cheers!
And yes, my DB is pretty large, actually about 620 Mb.
Ok, I will set the TRACE mode as suggested next time if UMS will have an issue. Thank you!
Cheers!
Re: UMS closes by itself
Posted: Wed Feb 12, 2025 2:59 am
Hi there, it happened again Now I could run UMS in TRACE mode, please find the zip attached. I'm not sure but it seems that UMS went down just before (or while) I connected to the computer where the UMS was running via RDP. The "old GUI" was definitely not running at that moment! And it seems to me that there was kind of network issue which caused that crash (I mean the very last messages in the log file). Maybe important for your investigation: the hard disk, which is being indexed, is an external 8TB drive connected via USB3 to the computer, thus going from time to time in "sleep" mode.
Now I could run UMS in TRACE mode, please find the zip attached. I'm not sure but it seems that UMS went down just before (or while) I connected to the computer where the UMS was running via RDP. The "old GUI" was definitely not running at that moment! And it seems to me that there was kind of network issue which caused that crash (I mean the very last messages in the log file). Maybe important for your investigation: the hard disk, which is being indexed, is an external 8TB drive connected via USB3 to the computer, thus going from time to time in "sleep" mode.Re: UMS closes by itself
Posted: Thu Feb 13, 2025 7:27 am
Those logs were not complete so could not see the first cause of the memory problem.
Please use the packing option in UMS to include all the logs as it splits them up and zips them when reaching a certain size. Only the vey end was included in the 7z.
You can exclude the debug.log.prev.zip file as this will be from when UMS last ran and will be the largest in this case.
As you have TRACE mode enabled then the the prev logs are not needed anyway.
The first memory error is from a .jpg but I think this is at the end of a series of events from the original cause.
There are some warnings about the IP 192.168.178.173 with "Device descriptor retrieval failed". Is this the computer you are remoting in from?
I just thought that maybe the problem is with your RAM and it could be failing. See if you can do a memory test with something like Memtest
One of my memory sticks started to fail a few years ago and was causing strange problems with the system till I discovered the cause.
Please use the packing option in UMS to include all the logs as it splits them up and zips them when reaching a certain size. Only the vey end was included in the 7z.
You can exclude the debug.log.prev.zip file as this will be from when UMS last ran and will be the largest in this case.
As you have TRACE mode enabled then the the prev logs are not needed anyway.
The first memory error is from a .jpg but I think this is at the end of a series of events from the original cause.
Code: Select all
/ums/media/a8011eb9-f144-4e6c-bba0-8f7fd862d264/1073456/JPEG_SM_20240826_164521.jpg
java.lang.OutOfMemoryError: Java heap space
at java.desktop/java.awt.image.DataBufferByte.<init>(Unknown Source)
at java.desktop/java.awt.image.Raster.createInterleavedRaster(Unknown Source)
at java.desktop/java.awt.image.BufferedImage.<init>(Unknown Source)
at net.coobird.thumbnailator.builders.BufferedImageBuilder.build(Unknown Source)
at net.coobird.thumbnailator.makers.ThumbnailMaker.makeThumbnail(Unknown Source)
at net.coobird.thumbnailator.makers.ScaledThumbnailMaker.make(Unknown Source)
at net.coobird.thumbnailator.Thumbnailator.createThumbnail(Unknown Source)
at net.coobird.thumbnailator.Thumbnails$Builder.toOutputStream(Unknown Source)
at net.pms.image.ImagesUtil.transcodeImage(ImagesUtil.java:1156)
at net.pms.image.ImagesUtil.transcodeImage(ImagesUtil.java:892)
at net.pms.image.ImagesUtil.transcodeImage(ImagesUtil.java:580)
at net.pms.dlna.DLNAImage.toDLNAImage(DLNAImage.java:375)
at net.pms.dlna.DLNAImageInputStream.toImageInputStream(DLNAImageInputStream.java:144)
at net.pms.network.mediaserver.servlets.MediaServerServlet.sendMediaResponse(MediaServerServlet.java:411)
at net.pms.network.mediaserver.servlets.MediaServerServlet.doGetHead(MediaServerServlet.java:164)
at net.pms.network.mediaserver.servlets.MediaServerServlet.doGet(MediaServerServlet.java:88)
at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:527)
at net.pms.network.mediaserver.servlets.MediaServerHttpServlet.service(MediaServerHttpServlet.java:35)
at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:614)
at org.eclipse.jetty.ee10.servlet.ServletHolder.handle(ServletHolder.java:736)
at org.eclipse.jetty.ee10.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1619)
at org.eclipse.jetty.ee10.servlet.ServletHandler$MappedServlet.handle(ServletHandler.java:1552)
at org.eclipse.jetty.ee10.servlet.ServletChannel.dispatch(ServletChannel.java:819)
at org.eclipse.jetty.ee10.servlet.ServletChannel.handle(ServletChannel.java:436)
at org.eclipse.jetty.ee10.servlet.ServletHandler.handle(ServletHandler.java:469)
at org.eclipse.jetty.server.handler.ContextHandler.handle(ContextHandler.java:1060)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:151)
at org.eclipse.jetty.server.Server.handle(Server.java:182)
at org.eclipse.jetty.server.internal.HttpChannelState$HandlerInvoker.run(HttpChannelState.java:662)
at org.eclipse.jetty.server.internal.HttpConnection.onFillable(HttpConnection.java:418)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:322)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:99)I just thought that maybe the problem is with your RAM and it could be failing. See if you can do a memory test with something like Memtest
One of my memory sticks started to fail a few years ago and was causing strange problems with the system till I discovered the cause.