Hello Synchronauts
Dunno how, but here sometime after the last pull and rebuild (in the last week) I lost most of mt file areas, all that was left was my main file areas. luckily I believe the file.1.ini was my last backup so I copied it back to file.ini.
I don't know what caused this to happen, I've done nothing except the last pull, which I see some files was moved around, deleted, and added. but it does'nt appear that anything should have affected file.ini. and I've done nothing to change any of the file areas, or delete them.. so yeah.. thats a bit strange.
Any Ideas what may have caused this??
areas. luckily I believe the file.1.ini was my last backup so I copied it back to file.ini.
Re: file.ini issues
By: kk4qbn to All on Wed Jan 29 2025 01:42 pm
Hello Synchronauts
Dunno how, but here sometime after the last pull and rebuild (in the last week) I lost most of mt file areas, all that was left was my main file areas. luckily I believe the file.1.ini was my last backup so I copied it back to file.ini.
I don't know what caused this to happen, I've done nothing except the last pull, which I see some files was moved around, deleted, and added. but it does'nt appear that anything should have affected file.ini. and I've done nothing to change any of the file areas, or delete them.. so yeah.. thats a bit strange.
Any Ideas what may have caused this??
Sounds like I may have broken something with commit f05b4c80a325a887.
I'll experiment and try to repo (and obviously fix) ASAP. Sorry about that, glad we back up! :-)
I haven't been able to reproduce the problem described. Maybe try updating to the latest and see if you can still reproduce the issue? Also, detailed comparison/diff of your before/after file.ini file might be helpful if/when it occurs again.
Re: file.ini issues
By: Digital Man to kk4qbn on Wed Jan 29 2025 11:51:14
I haven't been able to reproduce the problem described. Maybe try updating to the latest and see if you can still reproduce the issue? Also, detailed comparison/diff of your before/after file.ini file might be helpful if/when it occurs again.
I have a fresh build as of right after that message was posted, if I notice that it happens again I'll see if I can do some digging.. afaik I should have done nothing that would have deleted, changed that.. very strange. the only way I really noticed it is that I went from having close to 200,000 something files to 14 and a saw it when I was checking email from the website..
Hopefully this wont happen again, I'll go look at file.0.ini and see what it looks like. check sizes, etc.
Yeah, I'm curious what the corrupted/bad/truncated file.ini file looks/looked like. The files are human readable, so you can use standard text tools like diff if you wish. If it was caused by a bug in SCFG, it would be triggered by making a change to any file options/areas and saving the changes.
Yeah, I'm curious what the corrupted/bad/truncated file.ini file looks/looked like. The files are human readable, so you can use standard text tools like diff if you wish. If it was caused by a bug in SCFG, it would be triggered by making a change to any file options/areas and saving
Re: file.ini issues
By: Digital Man to kk4qbn on Wed Jan 29 2025 16:51:42
Yeah, I'm curious what the corrupted/bad/truncated file.ini file looks/looked like. The files are human readable, so you can use standard text tools like diff if you wish. If it was caused by a bug in SCFG, it would be triggered by making a change to any file options/areas and saving
I copied my file.ini over to file.bak, went into scfg and changed a file area name in my first file area, its hard for me to make heads or tails out of anything with diff, but the old file.bak filesize is 858674 and the new file.ini is 964001.
dunno if that tells you anything but it seems like a
fairly large difference for a 1 word change in the file area.
But, I am not seeing the same issue I had so hopefully it was just a 1 off issue. sometimes shit just happens :-)
Re: file.ini issues
By: Digital Man to kk4qbn on Wed Jan 29 2025 16:51:42
Yeah, I'm curious what the corrupted/bad/truncated file.ini file looks/looked like. The files are human readable, so you can use standard text tools like diff if you wish. If it was caused by a bug in SCFG, it would be triggered by making a change to any file options/areas and saving the changes.
Thats what is strange is I have'nt made any changes to my file areas, in ages. I will though just to see if I can get it to happen again.
Also I've noticed around the same time that my oneliners module has stopped working. when I try to run it, it says it doesnt exist. and it is sitting right where it's been located all the time in ../xtrn/oneliners I checked the xtrn.*.ini files and the last 4 or so are the same size so there has been no change to them.
maybe these two issues have nothing to do with each other, I thought I might as well mention it though because the only changes I've made lately to my bbs has been keeping the build updated.
Use a tool like diff to compare them?
File system issue maybe? Are you low on disk space?
Well lets look into the onliners module issue - how do you have it configured in SCFG? What's the error message exactly?
ONELINERS
Re: file.ini issues
By: Digital Man to kk4qbn on Thu Jan 30 2025 11:39:22
Use a tool like diff to compare them?
When I learn to use it I definatly will :) It just spit a bunch of text onto the screen with no real context as to what it was.
If the issue ever happens again I'll give it a try.
File system issue maybe? Are you low on disk space?
No. Plenty of disk space remaining. seen no read or write errors, I have a few times through last year get a "too many files open" error in synchronet and it would stop reading/writing etc. I've had to boost the open files a couple times. but that issue has'nt came up in a long time.
Re: file.ini issues
By: Digital Man to kk4qbn on Thu Jan 30 2025 11:41:41
Well lets look into the onliners module issue - how do you have it configured in SCFG? What's the error message exactly?
³Name oneliners
³Internal Code ONELINER
³Start-up Directory ../xtrn/oneliners/
³Command Line ?oneliners.js
³Clean-up Command Line
³Execution Cost None
³Access Requirements
³Execution Requirements REST NOT G
³Multiple Concurrent Users Yes
³I/O Method FOSSIL or UART
³Native Executable No
³Use Shell or New Context No
³Modify User Data No
³Execute on Event No
³Pause After Execution No
³Disable Local Display No
³BBS Drop File Type None
../xtrn/onliners/oneliners.js does exist
this is the error:
1/30 18:25:04 term Node 1 <kk4qbn> Oneliners error: Error: Unknown module: ONELINERS
??
Sysop: | Luis Silva |
---|---|
Location: | Lisbon |
Users: | 763 |
Nodes: | 10 (0 / 10) |
Uptime: | 196:09:38 |
Calls: | 247 |
Files: | 46,971 |
Messages: | 12,329 |