![]() ![]() ![]() Then the only thing that was running was the web progress monitor and that kept failing every time to update progress 11.46.40:EST:CmdRemote:lambda$start$114:SEVERE: >/fixsongs.update_progressīut I still dont know what is using up the file descriptors in the first place.# A fatal error has been detected by the Java Runtime Environment: 11.46.40:EST:ServerFixSongs$Task:run:SEVERE: nullĪt java.io.FileOutputStream.(FileOutputStream.java:203)Īt .AbstractReport.getUTF8Writer(AbstractReport.java:185)Īt .AbstractReport.outputErrors(AbstractReport.java:258)Īt .FixSongsReportCreator.createBodyOfReport(FixSongsReportCreator.java:116) 11.46.40:EST:AbstractReport:outputErrors:WARNING: Report 2:end ![]() 11.46.40:EST:AbstractReport:outputErrors:WARNING: Report 2:start Java.io.IOException: No file descriptors availableĪt java.io.UnixFileSystem.createFileExclusively(Native Method)Īt java.io.File.createNewFile(File.java:1012)Īt .AbstractReport.createSectionFile(AbstractReport.java:132)Īt .tupHeaderAndPages(AbstractReport.java:340)Īt .tupHeaderAndPages(FixSongsReport.java:167)Īt .nfigureReport(FixSongsReport.java:155)Īt .FixSongsReportCreator.createBodyOfReport(FixSongsReportCreator.java:37)Īt .(FixSongsController.java:304)Īt .callback.ServerFixSongs$n(ServerFixSongs.java:731)Īt $RunnableAdapter.call(Executors.java:511)Īt .run(FutureTask.java:266)Īt .runWorker(ThreadPoolExecutor.java:1149)Īt $n(ThreadPoolExecutor.java:624) Oh I see now that I have reviewed the logs, once it started getting file descriptor errors it carried on, and then eventually gave up and tried to create report but then that failed with: 11.46.40:EST:AbstractReport:createSectionFile:SEVERE: No file descriptors available ![]() In the meantime I will set up a test on an actual nas docker instance. Actually since songkong_debug0-0.log is one file I can’t see how you could have more than file descriptor open on it, are you sure there are multiple file descriptors for this file at the same time since it is not clear from your output. Lr-x- 1 root root 64 Jan 30 09:52 371 -> /mnt/app/share/log/SongKong/Database/EhCache/file/ArtistArtworkCache_64e9f1ef1e593fb741fdc9e97d5aa2a7cffe44cf/offheap-disk-store/ehcache-disk-store.dataĪnd I can see only one file descriptor for songkong_debug0-0.log. I’m running lsof on a standard linux machine and so far the bulk of open files are just links to cache files but the number of these are not increasing, it is consistent at about 350 file descriptors in use. PS: What steps do you recommend i take now to resolve this fix songs issue so that Songkong will scan my complete music collection?Ĭonfused because this error would seem to only happen after creating a new report, and you are failing before get to this point. Can you determine why that log file is not releasing file descriptors? The line that i noticed that was using a ton of file descriptors seemed to be the debug log. The output of the songkong2.txt file indicated the following: I ssh’d via putty into my server and did the following commands to see if i could see how many file descriptors were in ~]# ps aux | grep songkongġ3719 admin S /sbin/tini /bin/sh -c /opt/songkong/songkongremote8.shġ3832 admin S ash /opt/songkong/songkongremote8.shġ3889 admin 13916340 S java -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -XX:MaxRAMFraction=2 2.log.MLog=2.14MLog =jdk .class=.StandardLogging -jar lib/songkong-6.8.jar -rĢ5060 admin 964 S grep ~]# lsof -p 13889 > songkong2.txt Songkong:server unable to recreate default page:/root/index.html: No file descriptors available So i viewed the songkong docker container log and saw the following messages: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |