|
|
Post by Alyce on May 19, 2009 12:40:03 GMT -5
I am having trouble using the KILL command on runbasicnet.com. I get a file sharing violation error. I don't think the file is open in my program. Is it verboten to kill files on the server, even in one's own account?
|
|
|
|
Post by Jerry Muelver on May 19, 2009 13:22:30 GMT -5
I'll check the permission business. At least, you should be able to kill files via FTP... unless I configured your account too conservatively.
|
|
|
|
Post by votan on May 19, 2009 13:29:05 GMT -5
I'm experiencing similar sharing violations from time to time.. even though the file should be closed, it still seems to be open. Most probably caused by terminating code to early or not printing out all errors etc..... I'm not a runbasicnet.com user... so I do not know what level of access you have to the server? Can you shut down and restart the RB server? After that you probably can delete the file again... what on the other hand means your file remained open... so you will need to check your code. While developing, I always print out "open" or "close" upon every open/close I do, to visually see if all open/close commands were executed. This helped me a lot to find out when a file did not get closed when it should.
Doesn't sound like a permission thing though.... else it would give another error but not a sharing violation.
|
|
|
|
Post by Alyce on May 19, 2009 13:32:53 GMT -5
Thanks. I can try via FTP, but I wanted to find out about using KILL. It's an SQL db file. (I always disconnect immediately after making a query.) I've changed the structure and the easiest way to manage is to kill the file, since it is a fledgling program. In the meantime, I've simply changed the name of the db file, but that method could quickly fill the server space.  |
|
|
|
Post by Jerry Muelver on May 19, 2009 15:26:49 GMT -5
Can you create and kill other files, for instance a text file?
|
|
|
|
Post by Alyce on May 19, 2009 16:35:52 GMT -5
Can you create and kill other files, for instance a text file? Yup. Can create and KILL sequential files. DB file not in use, but still cannot delete it, even when not using the program that created it. Odd, yes? Tried to delete via FTP with no success. |
|
|
|
Post by votan on May 19, 2009 18:32:31 GMT -5
Yeah... the RB Server keeps it open.... you'll have to restart RB server in order to unlock the file again. Looks like Carl needs to add a bit more controll options to the server.... Well, the options "start / stop serving" are there, but have no effect yet... This would probably solve the problem... if you could access the server consele. So we need an option to restart the server remotely for easy emergency rebooting. Hmmm I'll check if I can do it via a DOS batch file..... that then can be called remotely through a RB script...
Edit: Ok, got it working here.... will try to create a safe batch... but need some sleep first now....
Edit 2: Ok, Batch is done and works just fine. Now we only have a problem with multiple instances.... they are all called rbp.exe... and that's where the problem starts.... one instance is easy to kill and restart... but with more than one instance, we need to know the PID of each instance, else we kill the wrong instance. I gonna look into that tomorrow and will hopefully come up with something.
Oh....and I need to know what windows version is running on runbasicnet.com as some of the needed commands are not available on all versions.
|
|
|
|
Post by StefanPendl on May 20, 2009 1:31:00 GMT -5
Oh....and I need to know what windows version is running on runbasicnet.com as some of the needed commands are not available on all versions. Windows Server 2003, I think, the newer hosting services use that or Linux. Each process know the fully qualified path of the executable it is started with, so you can look for that. Jerry has separated the accounts into one folder each, I think.
The best is to correctly disconnect the DB file, which will be needed anyways, seems there needs to be one more problem fixed. |
|
|
|
Post by votan on May 20, 2009 4:33:20 GMT -5
Yeah well, getting the path for each process via windows is easy, the problem is doing it with the help of DOS. I would need to analyze logfiles.. either system logs or logs from third party tools. Not to bad, but there would be a much easier way to do this.... giving each customer a uniquely named rbp.exe file.
Anyway, I just found a solution to do it without renaming but it requires a bit more parsing of dos output etc.... but therefore it will be more flexible. I'll try to get it done today... or at least tomorrow.
The problem for runbasicnet.com users is, that once they missed to close a file during testing or so, RB will keep the file open. And they don't have a way to close that file again.
The program will allow everyone (private users and runbasicnet.com users) to either just close all open files or to completly reboot their RB server. I have it working here so far, but need to write some wrap around RB code now and add some security.
|
|
|
|
Post by Jerry Muelver on May 20, 2009 6:30:56 GMT -5
I rebooted Alyce's RB server. Did that do the trick for you, Alyce?
|
|
|
|
Post by Alyce on May 20, 2009 6:43:34 GMT -5
Jerry, yes it works now. In fact, I created, then KILLed a couple of DB files with no problem. Thanks.
|
|
|
|
Post by votan on May 20, 2009 20:50:09 GMT -5
So far so bad.... The RB server is not behaving as it should! the restarted server always listens on the default port 8008, while the config file says 8080. So it seems like the restarted version can not read the config file and so starts on the default port that is set somewhere in the RBserver code itself. Carl.... is there an additional command line parameter to define the configfile to start with? So like c:\rbp\rbp.exe tb.im config.xml ?
But whatever, I'll get it to work... might need it for a futere project as well..
|
|
|
|
Post by Alyce on May 21, 2009 5:21:50 GMT -5
Votan, you might want to report this on the bug report board, or discuss it on a different board. This board is specific to the runbasicnet.com hosting service. I use this service to host my RB server. Jerry rebooted it for me and I can again delete files.
It may be a bug in RB, or something general and not specific to the runbasicnet.com server.
|
|
|
|
Post by votan on May 21, 2009 7:56:30 GMT -5
Well, this issue does not really seem to be a bug.... and my app entirely just is for servers hosting multiple instances of RBP.... so basically just for runbasicnet.com and my own server. (even though there will be a lite version for single instance users)
And as soon as you miss to close a file correctly again, this issue will come up again. And always having Jerry to reboot your server manually is not the best option. I think it would be much more comfortable, if users could do it themself. I'm just trying to help.....
So, anyway... the problem seems to be just a path settings problem in DOs... so it will be fixed. My app laso allows you to display all open files for each account and close/delete them selectively. And it shows some server stats.. just for the fun of it.
Anyway, I gonna move over to RB Code or projects....
|
|
|
|
Post by Alyce on May 21, 2009 9:55:58 GMT -5
And as soon as you miss to close a file correctly again, this issue will come up again. And always having Jerry to reboot your server manually is not the best option. I think it would be much more comfortable, if users could do it themself. I agree. (Much as I enjoy pestering Jerry...) |
|
