Menu
▾
▴
bobs-devel
|
From: James W. B. <vi...@ea...> - 2004-05-13 19:45:29
|
Hi all: I've just installed the new version of Bobs and I'm getting the following error when running check configuration on a share that is smb mounted. The mount and unmount are successful, but this is the failure I'm getting. Any ideas why? Thanks James Attempting to write, read and delete a file on /backup/bobsdata/current/process/mounts/atladm/msde FAIL Write file test failed with these messages: /backup/bobsdata/current/process/cmd/cmd.1084473105.bash: line 9: /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: No such file or directory cat: /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: No such file or director |
|
From: Joe Z. <joe...@za...> - 2004-05-13 20:33:59
|
James W. Beauchamp wrote: >Hi all: >I've just installed the new version of Bobs and I'm getting the following error when running check configuration on a share that is smb mounted. The mount and unmount are successful, but this is the failure I'm getting. Any ideas why? > >Thanks > >James > >Attempting to write, read and delete a file on >/backup/bobsdata/current/process/mounts/atladm/msde FAIL >Write file test failed with these messages: >/backup/bobsdata/current/process/cmd/cmd.1084473105.bash: line 9: /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: No such file or directory >cat: /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: No such file or director > > > Is the msde share on atladm shared for write access? Joe |
|
From: James W. B. <jbe...@mi...> - 2004-05-13 20:35:53
|
No, the share is only for read access. Just for the heck of it I went ahead and did Backup Now and it worked, so I'm not sure what the deal is. James Joe Zacky wrote: > > > James W. Beauchamp wrote: > >> Hi all: >> I've just installed the new version of Bobs and I'm getting the >> following error when running check configuration on a share that is >> smb mounted. The mount and unmount are successful, but this is the >> failure I'm getting. Any ideas why? >> >> Thanks >> >> James >> >> Attempting to write, read and delete a file on >> /backup/bobsdata/current/process/mounts/atladm/msde FAIL >> Write file test failed with these messages: >> /backup/bobsdata/current/process/cmd/cmd.1084473105.bash: line 9: >> /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: >> No such file or directory >> cat: >> /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: >> No such file or director >> >> > Is the msde share on atladm shared for write access? > > Joe > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > Bobs-devel mailing list > Bob...@li... > https://lists.sourceforge.net/lists/listinfo/bobs-devel > |
|
From: James W. B. <jbe...@mi...> - 2004-05-13 20:38:22
|
As a side issue, none of the shares that I'm backing up with Bobs is set up for restore. And I just noticed that when I go to the normal interface to view those files backed up, it says No Servers with Restore Ability Present, so I can't even look at what I've backed up. Is that a bug? Seems like you should be able to look at what's there even if you're not going to be using the Bobs automated restore method. Just my thoughts. James James W. Beauchamp wrote: > No, the share is only for read access. Just for the heck of it I went > ahead and did Backup Now and it worked, so I'm not sure what the deal is. > James > > > Joe Zacky wrote: > >> >> >> James W. Beauchamp wrote: >> >>> Hi all: >>> I've just installed the new version of Bobs and I'm getting the >>> following error when running check configuration on a share that is >>> smb mounted. The mount and unmount are successful, but this is the >>> failure I'm getting. Any ideas why? >>> >>> Thanks >>> >>> James >>> >>> Attempting to write, read and delete a file on >>> /backup/bobsdata/current/process/mounts/atladm/msde FAIL >>> Write file test failed with these messages: >>> /backup/bobsdata/current/process/cmd/cmd.1084473105.bash: line 9: >>> /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: >>> No such file or directory >>> cat: >>> /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: >>> No such file or director >>> >>> >> Is the msde share on atladm shared for write access? >> >> Joe >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: SourceForge.net Broadband >> Sign-up now for SourceForge Broadband and get the fastest >> 6.0/768 connection for only $19.95/mo for the first 3 months! >> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click >> _______________________________________________ >> Bobs-devel mailing list >> Bob...@li... >> https://lists.sourceforge.net/lists/listinfo/bobs-devel >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > Bobs-devel mailing list > Bob...@li... > https://lists.sourceforge.net/lists/listinfo/bobs-devel > |
|
From: AWC M. L. <mai...@aw...> - 2004-05-13 20:39:48
|
I just ran across something familiar. Check to ensure that the machine with bobs installed actually has created the directory being mapped to. Check the line before your error message for creating the mount. Get to a command prompt and try and enter the command yourself. Substitute what your server suggests. I had something similar to: smbmount "//servername/bobs" "/var/bobsdata/current/process/mounts/backup/Shared" -o username=something,password='here' &>/dev/null I actually received an error message when I entered this command even though bobs said it was fine. In my case the directory: "/var/bobsdata/current/process/mounts/backup/Shared" did not exist. Bobs did not seem to create it. So I created the directory and I could mount the remote dictory successfully. Next I tried copying a file to "/var/bobsdata/current/process/mounts/backup/Shared" logged in with the username above. (Not as root.) I ended up getting rights errors where I could not copy the file across. So I corrected that as well. Once all that was done I was able to get a backup running. -- Charles James W. Beauchamp wrote: > Hi all: > I've just installed the new version of Bobs and I'm getting the following error when running check configuration on a share that is smb mounted. The mount and unmount are successful, but this is the failure I'm getting. Any ideas why? > > Thanks > > James > > Attempting to write, read and delete a file on > /backup/bobsdata/current/process/mounts/atladm/msde FAIL > Write file test failed with these messages: > /backup/bobsdata/current/process/cmd/cmd.1084473105.bash: line 9: /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: No such file or directory > cat: /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: No such file or director > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > Bobs-devel mailing list > Bob...@li... > https://lists.sourceforge.net/lists/listinfo/bobs-devel > |
|
From: James W. B. <jbe...@mi...> - 2004-05-13 21:09:29
|
Charles: No sooner had I deleted your message with the fix for changing "n" to "c" (or whatever it was) in the code did I notice that I too have that problem. Can you kindly forward that mail one more time so I can fix that in my install as well? [ Could not create a database of type db3 or db4 (tried both) *Warning*: no such handler: in */var/www/html/bobs/inc/class_db.php* on line *79]* Thanks James AWC Mailing Lists wrote: > I just ran across something familiar. Check to ensure that the > machine with bobs installed actually has created the directory being > mapped to. > > Check the line before your error message for creating the mount. Get > to a command prompt and try and enter the command yourself. > Substitute what your server suggests. I had something similar to: > > smbmount "//servername/bobs" > "/var/bobsdata/current/process/mounts/backup/Shared" -o > username=something,password='here' &>/dev/null > > I actually received an error message when I entered this command even > though bobs said it was fine. > > In my case the directory: > "/var/bobsdata/current/process/mounts/backup/Shared" did not exist. > Bobs did not seem to create it. So I created the directory and I could > mount the remote dictory successfully. > > Next I tried copying a file to > "/var/bobsdata/current/process/mounts/backup/Shared" logged in with > the username above. (Not as root.) > > I ended up getting rights errors where I could not copy the file > across. So I corrected that as well. > > Once all that was done I was able to get a backup running. > > -- Charles > > > > > > James W. Beauchamp wrote: > >> Hi all: >> I've just installed the new version of Bobs and I'm getting the >> following error when running check configuration on a share that is >> smb mounted. The mount and unmount are successful, but this is the >> failure I'm getting. Any ideas why? >> >> Thanks >> >> James >> >> Attempting to write, read and delete a file on >> /backup/bobsdata/current/process/mounts/atladm/msde FAIL >> Write file test failed with these messages: >> /backup/bobsdata/current/process/cmd/cmd.1084473105.bash: line 9: >> /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: >> No such file or directory >> cat: >> /backup/bobsdata/current/process/mounts/atladm/msde/bobswritetest.out: >> No such file or director >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: SourceForge.net Broadband >> Sign-up now for SourceForge Broadband and get the fastest >> 6.0/768 connection for only $19.95/mo for the first 3 months! >> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click >> _______________________________________________ >> Bobs-devel mailing list >> Bob...@li... >> https://lists.sourceforge.net/lists/listinfo/bobs-devel >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > Bobs-devel mailing list > Bob...@li... > https://lists.sourceforge.net/lists/listinfo/bobs-devel > |
|
From: Joe Z. <joe...@za...> - 2004-05-13 21:22:30
|
James W. Beauchamp wrote: > Charles: > No sooner had I deleted your message with the fix for changing "n" to > "c" (or whatever it was) in the code did I notice that I too have that > problem. Can you kindly forward that mail one more time so I can fix > that in my install as well? And you emptied your trash too!? This is a known issue that will be fixed on the next release. It's described here: http://us4.php.net/manual/en/function.dba-open.php The problem is in /var/www/html/bobs/inc/class_db.php. Change the "c" in both @dba_open functions to "n" and it should work fine. 43 // check what dba type we should use 44 $tmpfile = tempnam("/tmp", "BOBS"); 45 $dbcheck = @dba_open($tmpfile, "c", "db3"); 46 if ( $dbcheck === FALSE ) { 47 $dbcheck = @dba_open($tmpfile, "c", "db4"); 48 if ( $dbcheck === FALSE ) { Cheers, Joe |
|
From: Joe Z. <joe...@za...> - 2004-05-13 20:54:07
|
James W. Beauchamp wrote: > As a side issue, none of the shares that I'm backing up with Bobs is > set up for restore. And I just noticed that when I go to the normal > interface to view those files backed up, it says No Servers with > Restore Ability Present, so I can't even look at what I've backed up. > Is that a bug? Seems like you should be able to look at what's there > even if you're not going to be using the Bobs automated restore method. > > Just my thoughts. > > James I wouldn't consider it a bug. You can look at the files with your file browser. I think Rene would be the ultimate authority to decide whether you should be able to view the files if they're not setup for restore. > > > James W. Beauchamp wrote: > >> No, the share is only for read access. Just for the heck of it I >> went ahead and did Backup Now and it worked, so I'm not sure what the >> deal is. >> James >> >> The "Check Configuration" always tries to write, read, and delete a file to the backup share and the restore share. It's not checking that you only have it setup for backup, so this error can be ignored since your backups are working. Joe |
|
From: James W. B. <jbe...@mi...> - 2004-05-13 20:57:44
|
thanks Joe. James Joe Zacky wrote: > > > James W. Beauchamp wrote: > >> As a side issue, none of the shares that I'm backing up with Bobs is >> set up for restore. And I just noticed that when I go to the normal >> interface to view those files backed up, it says No Servers with >> Restore Ability Present, so I can't even look at what I've backed >> up. Is that a bug? Seems like you should be able to look at what's >> there even if you're not going to be using the Bobs automated restore >> method. >> >> Just my thoughts. >> >> James > > > I wouldn't consider it a bug. You can look at the files with your file > browser. I think Rene would be the ultimate authority to decide > whether you should be able to view the files if they're not setup for > restore. > >> >> >> James W. Beauchamp wrote: >> >>> No, the share is only for read access. Just for the heck of it I >>> went ahead and did Backup Now and it worked, so I'm not sure what >>> the deal is. >>> James >>> >>> > The "Check Configuration" always tries to write, read, and delete a > file to the backup share and the restore share. It's not checking that > you only have it setup for backup, so this error can be ignored since > your backups are working. > > Joe > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > Bobs-devel mailing list > Bob...@li... > https://lists.sourceforge.net/lists/listinfo/bobs-devel > |
|
From: Jochen M. <ml...@om...> - 2004-05-14 09:55:55
|
Hi, Am Do, 2004-05-13 um 22.53 schrieb Joe Zacky: > James W. Beauchamp wrote: > > > As a side issue, none of the shares that I'm backing up with Bobs is > > set up for restore. And I just noticed that when I go to the normal > > interface to view those files backed up, it says No Servers with > > Restore Ability Present, so I can't even look at what I've backed up. > > Is that a bug? Seems like you should be able to look at what's there > > even if you're not going to be using the Bobs automated restore method. > > > > Just my thoughts. > > > > James > > I wouldn't consider it a bug. You can look at the files with your file > browser. I think Rene would be the ultimate authority to decide whether > you should be able to view the files if they're not setup for restore. > Well, I have implemented this. The thing is that a user who logs in, wants to restore some stuff, not actually look, what he has backupped. (IMHO I implemented this, because, an error came up, when no restore was enabled). What do you think, Rene? > > > > > > James W. Beauchamp wrote: > > > >> No, the share is only for read access. Just for the heck of it I > >> went ahead and did Backup Now and it worked, so I'm not sure what the > >> deal is. > >> James > >> > >> > The "Check Configuration" always tries to write, read, and delete a file > to the backup share and the restore share. It's not checking that you > only have it setup for backup, so this error can be ignored since your > backups are working. > > Joe > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > Bobs-devel mailing list > Bob...@li... > https://lists.sourceforge.net/lists/listinfo/bobs-devel -- omatix.de internet services omatix solutions & trainings omatix onlineverlag Jochen Metzger j.m...@om... Telefon +49(30) 78709298 Fax +49(30) 78709296 -- Hosting für Ihr Business: http://hosting.omatix.de |
|
From: Rene R. <re...@gr...> - 2004-05-14 10:30:21
|
On Thu, 2004-05-13 at 22:53, Joe Zacky wrote: > James W. Beauchamp wrote: > > > As a side issue, none of the shares that I'm backing up with Bobs is > > set up for restore. And I just noticed that when I go to the normal > > interface to view those files backed up, it says No Servers with > > Restore Ability Present, so I can't even look at what I've backed up. > > Is that a bug? Seems like you should be able to look at what's there > > even if you're not going to be using the Bobs automated restore method. > > > > Just my thoughts. > > > > James > > I wouldn't consider it a bug. You can look at the files with your file > browser. I think Rene would be the ultimate authority to decide whether > you should be able to view the files if they're not setup for restore. > > > I would suggest a checkbox on the admin page to explicitly allow/disallow users access to the interface for each share I can't remember if there are any problem related to browsing something you can't restore, and I don't have time to check into it at the moment. Cheers Rene |
Thanks for helping keep SourceForge clean.
X