1
Setup & Installation / Re: Troubleshooting process trap/dump...how?
« on: May 07, 2025, 05:30:10 pm »
UPDATE
======
OK, so perhaps not the real RC for the re-boot issue - I'm still working through that - but I do know what was causing the RSYNC issues I recently started to see.
In short: I have been experiencing problems with Lucide and opening PDFs that are stored on my NAS box.
Opening a single PDF is fine, 90% of the time I can open the 2nd one, 75% of the time I can open the 3rd one, but eventually Lucide comes up and no content shows and Lucide hangs. I can normally use the WPS TaskList to kill that Lucide instance, all others previously opened stay working, re-open the last doc and for the most part that's OK.
This only happens when I open multiple PDFs, which normally isn't the case, so for the most part it's not a big deal...but you know: when it becomes a nuisance is when you do in fact want multiple PDFs open, well, it was time to dig into this.
Seemingly the older versions of the Samba client & NetDrive plugins didn't show this, or at least I do not recall ever having these problems...so off I went redeploying older Samba Client & NetDrive combinations.
The combo I deployed most recently was samba-client-4.10.10-0.oc00.i686.rpm & ndpsmb-3.6.0-20190420.wpi, which means I was running Samba 4.10.10 client and NetDrive 3.6.0 plugin. (client stuff going into \usr\local\bin & \lib locations, etc.)
That did in fact improve my Lucide situation, considerably so, although not entirely.
HOWEVER
...what I did not know is that this combination (or most likely the Samba client) did mess around with the file DATES!!!
Sooo....the local & NAS dates would no longer match, as in: neither the CREATE nor MODIFIED dates were matching, and I couldn't determine what the pattern was either.
This in turn explained the strange RSYNC LOG results I would see where the most recent run of RSYNC if immediately re-ran would right away cause massive discrepancies (given my RYSNC options to match on MODIFIED dates and correct them).
I have now moved to samba-client-4.11.5-0.oc00.i686.rpm & ndpsmb-3.7.3-samba411-20220108.zip, which does correctly show the DATES...and that in turn has allowed RSYNC to breeze through it's regular runs because the vast majority of the files do NOT change.
So my RSYNC issue is "closed" now...lol
Appreciate all the feedback everyone!
======
OK, so perhaps not the real RC for the re-boot issue - I'm still working through that - but I do know what was causing the RSYNC issues I recently started to see.
In short: I have been experiencing problems with Lucide and opening PDFs that are stored on my NAS box.
Opening a single PDF is fine, 90% of the time I can open the 2nd one, 75% of the time I can open the 3rd one, but eventually Lucide comes up and no content shows and Lucide hangs. I can normally use the WPS TaskList to kill that Lucide instance, all others previously opened stay working, re-open the last doc and for the most part that's OK.
This only happens when I open multiple PDFs, which normally isn't the case, so for the most part it's not a big deal...but you know: when it becomes a nuisance is when you do in fact want multiple PDFs open, well, it was time to dig into this.
Seemingly the older versions of the Samba client & NetDrive plugins didn't show this, or at least I do not recall ever having these problems...so off I went redeploying older Samba Client & NetDrive combinations.
The combo I deployed most recently was samba-client-4.10.10-0.oc00.i686.rpm & ndpsmb-3.6.0-20190420.wpi, which means I was running Samba 4.10.10 client and NetDrive 3.6.0 plugin. (client stuff going into \usr\local\bin & \lib locations, etc.)
That did in fact improve my Lucide situation, considerably so, although not entirely.
HOWEVER
...what I did not know is that this combination (or most likely the Samba client) did mess around with the file DATES!!!
Sooo....the local & NAS dates would no longer match, as in: neither the CREATE nor MODIFIED dates were matching, and I couldn't determine what the pattern was either.
This in turn explained the strange RSYNC LOG results I would see where the most recent run of RSYNC if immediately re-ran would right away cause massive discrepancies (given my RYSNC options to match on MODIFIED dates and correct them).
I have now moved to samba-client-4.11.5-0.oc00.i686.rpm & ndpsmb-3.7.3-samba411-20220108.zip, which does correctly show the DATES...and that in turn has allowed RSYNC to breeze through it's regular runs because the vast majority of the files do NOT change.
So my RSYNC issue is "closed" now...lol
Appreciate all the feedback everyone!