from:"Julian Zielke"

Re: [BackupPC-users] Web Interface Doesn't Work after F27 Upgrade

2017-11-24 Thread Julian Zielke

Hi,

The User BackupPC is running under is missing in your statement. Please do the 
following on your config.pl:

cat config.pl | grep "^\$Conf{BackupPCUser}"

- Try accessing the CGI pm-files by using cat and sudo with this user.

- Execute "BackupPC_Admin" in /usr/share/BackupPC/bin using the user configured 
in your config.pl

- check of the following paths in your config.pl are correct:
$Conf{TopDir}
$Conf{ConfDir}
$Conf{LogDir}
$Conf{RunDir}
$Conf{InstallDir}
$Conf{CgiDir}

- Julian


-Ursprüngliche Nachricht-
Von: Tim Evans [mailto:tkev...@tkevans.com]
Gesendet: Freitag, 24. November 2017 13:44
An: Julian Zielke <jzie...@next-level-integration.com>
Betreff: Re: AW: [BackupPC-users] Web Interface Doesn't Work after F27 Upgrade

On 11/24/2017 03:37 AM, Julian Zielke wrote:
> What user is BackuPC running under? Normally it's "backuppc".

backuppc

>
> What permissions does the CGI bin and the binaries have? Please post an 
> ll-output of the directories.

# pwd
/usr/share/BackupPC/bin
# ls -l
total 544
-rwxr-xr-x 1 root root 80484 Aug  2 12:51 BackupPC -rwxr-xr-x 1 root root 16744 
Aug  2 12:51 BackupPC_Admin_SCGI -rwxr-xr-x 1 root root 11126 Aug  2 12:51 
BackupPC_archive -rwxr-xr-x 1 root root  5278 Aug  2 12:51 BackupPC_archiveHost 
-rwxr-xr-x 1 root root  3967 Aug  2 12:51 BackupPC_archiveStart -rwxr-xr-x 1 
root root  3514 Aug  2 12:51 BackupPC_attribPrint -rwxr-xr-x 1 root root 25976 
Aug  2 12:51 BackupPC_backupDelete -rwxr-xr-x 1 root root 17977 Aug  2 12:51 
BackupPC_backupDuplicate -rwxr-xr-x 1 root root 76573 Aug  2 12:51 
BackupPC_dump -rwxr-xr-x 1 root root  7659 Aug  2 12:51 
BackupPC_fixupBackupSummary -rwxr-xr-x 1 root root 14793 Aug  2 12:51 
BackupPC_fsck -rwxr-xr-x 1 root root  6481 Aug  2 12:51 BackupPC_ls -rwxr-xr-x 
1 root root 18055 Aug  2 12:51 BackupPC_migrateV3toV4 -rwxr-xr-x 1 root root 
13270 Aug  2 12:51 BackupPC_nightly -rwxr-xr-x 1 root root  2699 Aug  2 12:51 
BackupPC_poolCntPrint -rwxr-xr-x 1 root root 41817 Aug  2 12:51 
BackupPC_refCountUpdate -rwxr-xr-x 1 root root 20865 Aug  2 12:51 
BackupPC_restore -rwxr-xr-x 1 root root  7318 Aug  2 12:51 BackupPC_rrdUpdate 
-rwxr-xr-x 1 root root 15659 Aug  2 12:51 BackupPC_sendEmail -rwxr-xr-x 1 root 
root  2416 Aug  2 12:51 BackupPC_serverMesg -rwxr-xr-x 1 root root 20988 Aug  2 
12:51 BackupPC_tarCreate -rwxr-xr-x 1 root root 39838 Aug  2 12:51 
BackupPC_tarExtract -rwxr-xr-x 1 root root 40201 May 31 10:00 
BackupPC_tarExtract.save -rwxr-xr-x 1 root root  5333 Aug  2 12:51 
BackupPC_zcat -rwxr-xr-x 1 root root 10251 Aug  2 12:51 BackupPC_zipCreate

# pwd
/usr/share/BackupPC/lib/BackupPC/CGI
  ls -l
total 232
-rw-r--r-- 1 root root  1568 Aug  2 12:51 AdminOptions.pm
-rw-r--r-- 1 root root  2676 Aug  2 12:51 ArchiveInfo.pm
-rw-r--r-- 1 root root  9101 Aug  2 12:51 Archive.pm
-rw-r--r-- 1 root root 11712 Aug  2 12:51 Browse.pm
-rw-r--r-- 1 root root  7250 Aug  2 12:51 DirHistory.pm
-rw-r--r-- 1 root root 57687 Aug  2 12:51 EditConfig.pm
-rw-r--r-- 1 root root  2738 Aug  2 12:51 EmailSummary.pm
-rw-r--r-- 1 root root  6411 Aug  2 12:51 GeneralInfo.pm
-rw-r--r-- 1 root root 16644 Aug  2 12:51 HostInfo.pm
-rw-r--r-- 1 root root 18621 Aug  2 12:51 Lib.pm
-rw-r--r-- 1 root root  2959 Aug  2 12:51 LOGlist.pm
-rw-r--r-- 1 root root  2555 Aug  2 12:51 Queue.pm
-rw-r--r-- 1 root root  1491 Aug  2 12:51 ReloadServer.pm
-rw-r--r-- 1 root root  6879 Aug  2 12:51 RestoreFile.pm
-rw-r--r-- 1 root root  3457 Aug  2 12:51 RestoreInfo.pm
-rw-r--r-- 1 root root 12596 Aug  2 12:51 Restore.pm
-rw-r--r-- 1 root root  5044 Aug  2 12:51 RSS.pm
-rw-r--r-- 1 root root  2039 Aug  2 12:51 StartServer.pm
-rw-r--r-- 1 root root  3668 Aug  2 12:51 StartStopBackup.pm
-rw-r--r-- 1 root root  1650 Aug  2 12:51 StopServer.pm
-rw-r--r-- 1 root root  6454 Aug  2 12:51 Summary.pm
-rw-r--r-- 1 root root  8804 Aug  2 12:51 View.pm



--
Tim Evans|   5 Chestnut Court
|   Owings Mills, MD 21117
|   443-394-3864

Wichtiger Hinweis: Der Inhalt dieser E-Mail ist vertraulich und ausschließlich 
für den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene 
Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie 
bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung 
oder Weitergabe des Inhalts dieser E-Mail unzulässig ist. Wir bitten Sie, sich 
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen. Wir möchten 
Sie außerdem darauf hinweisen, dass die Kommunikation per E-Mail über das 
Internet unsicher ist, da für unberechtigte Dritte grundsätzlich die 
Möglichkeit der Kenntnisnahme und Manipulation besteht

Important Note: The information contained in this e-mail is confidential. It is 
intended solely for the addressee. Access to this e-mail by anyone else is 
unauthorized. If you are not the intended recipient, any form of disclosure, 
reproduction, distribution or any action taken or refrained from in reliance on 
it, is prohibited and may be un

Re: [BackupPC-users] Web Interface Doesn't Work after F27 Upgrade

2017-11-24 Thread Julian Zielke

What user is BackuPC running under? Normally it's "backuppc".

What permissions does the CGI bin and the binaries have? Please post an 
ll-output of the directories.

- Julian

-Ursprüngliche Nachricht-
Von: Tim Evans [mailto:tkev...@tkevans.com]
Gesendet: Donnerstag, 23. November 2017 18:23
An: General list for user discussion, questions and support 

Betreff: [BackupPC-users] Web Interface Doesn't Work after F27 Upgrade

Happy Thanksgiving.

Just upgraded my BackupPC server to Fedora 27 (from F26).  Service is running 
ok (there's a backup running right now).  Usual stuff in the LOG after the 
first boot of the upgraded system:

2017-11-23 10:27:50 Reading hosts file
2017-11-23 10:27:51 BackupPC started, pid 1130
2017-11-23 10:27:51 Next wakeup is 2017-11-23 11:00:00
2017-11-23 11:00:00 Next wakeup is 2017-11-23 12:00:00
2017-11-23 11:00:05 pelican: can't ping pelican (client = pelican); exiting
2017-11-23 12:00:00 Next wakeup is 2017-11-23 13:00:00
2017-11-23 12:00:02 Started full backup on pelican (pid=5320, share=C$)

But the Web interface doesn't work--httpd (Apache 2.4.29-1.fc27.x86_64) gives a 
503 error.

httpd error log says stuff like this:

[Thu Nov 23 10:52:26.203136 2017] [cgid:error] [pid 1162:tid 139834463086336] 
(13)Permission denied: [client ::1:43468] AH01257:
unable to connect to cgi daemon after multiple tries:
/usr/share/BackupPC/sbin/BackupPC_Admin, referer:
http://localhost/backuppc?action=summary

Similar errors come from trying to access other pages of the Web interface.  
httpd is serving normal HTML pages.

FYI, 'selinux' is totally disabled on this machine.
--
Tim Evans|5 Chestnut Court
443-394-3864|Owings Mills, MD 21117

--
Check out the vibrant tech community on one of the world's most engaging tech 
sites, Slashdot.org! http://sdm.link/slashdot 
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Wichtiger Hinweis: Der Inhalt dieser E-Mail ist vertraulich und ausschließlich 
für den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene 
Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie 
bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung 
oder Weitergabe des Inhalts dieser E-Mail unzulässig ist. Wir bitten Sie, sich 
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen. Wir möchten 
Sie außerdem darauf hinweisen, dass die Kommunikation per E-Mail über das 
Internet unsicher ist, da für unberechtigte Dritte grundsätzlich die 
Möglichkeit der Kenntnisnahme und Manipulation besteht

Important Note: The information contained in this e-mail is confidential. It is 
intended solely for the addressee. Access to this e-mail by anyone else is 
unauthorized. If you are not the intended recipient, any form of disclosure, 
reproduction, distribution or any action taken or refrained from in reliance on 
it, is prohibited and may be unlawful. Please notify the sender immediately. We 
also would like to inform you that communication via e-mail over the internet 
is insecure because third parties may have the possibility to access and 
manipulate e-mails.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Execute bash script after each share on backup server

2017-11-23 Thread Julian Zielke

Hi,

I've implemented some error checking in this script and it either exit with 0 
(ok) or 1 (fail).

The UserCmdCheckStatus has been activated and the Logfile of BackuPPC says:

2017-11-23 16:10:30 DumpPreShareCmd returned error status 256... exiting

But why Error 256 when it's 1? And the last Line the scripts outputs is:

2017-11-23 16:18:08 Output from DumpPreShareCmd: ERROR: Index * on *** 
corrupted or locked!

However on the host summary it says:

backup canceled by user (DumpPreShareCmd returned error status 0)

This doesn't make sense to me either, since it wasn't 0 but 1.

Anybody who can help me solving this problem?

- Julian

-Ursprüngliche Nachricht-
Von: Julian Zielke
Gesendet: Montag, 13. November 2017 08:55
An: 'General list for user discussion, questions and support' 
<backuppc-users@lists.sourceforge.net>
Betreff: AW: [BackupPC-users] Execute bash script after each share on backup 
server

Ok, Fi finally fixed it.

First of all I for shure know the difference between sh and bash. I just tried 
out different combinations, though my script doesn't make use of and bash-only 
syntax.

However: The PATH-Variable is not available when I execute I, so I added an 
export command at the beginning, resulting in my script working right.

The cleaner way would be to use absolute paths to the separate binaries, so 
I'll use /usr/bin/which  to invoke them properly.
Thanks anyway for your help. I'm glad the tool is so well supported by the 
community, although being free and opensource.

- Julian

-Ursprüngliche Nachricht-
Von: Julian Zielke
Gesendet: Montag, 13. November 2017 08:34
An: General list for user discussion, questions and support 
<backuppc-users@lists.sourceforge.net>
Betreff: AW: [BackupPC-users] Execute bash script after each share on backup 
server

Hi,

sorry for the confusion. I've tried with both arguments just for debugging 
purposes.

My script used the basename-command, which isn't available during execution so 
I changed that.
Now I get:

Executing DumpPostShareCmd: /bin/bash -c "/etc/BackupPC/notify.sh *arg1* *arg2*"
server01: -c: line 0: unexpected EOF while looking for matching `"'
server01: -c: line 1: syntax error: unexpected end of file

The command is:
/bin/bash -c "/etc/BackupPC/notify.sh $host $share $type $xferOK"

So what's unexpected here? I have to quote the scrit arguments, otherwise bash 
doesn't recognize them.

- Julian

-Ursprüngliche Nachricht-
Von: Holger Parplies [mailto:wb...@parplies.de]
Gesendet: Freitag, 10. November 2017 19:46
An: General list for user discussion, questions and support 
<backuppc-users@lists.sourceforge.net>
Betreff: Re: [BackupPC-users] Execute bash script after each share on backup 
server

Hi,

Les Mikesell wrote on 2017-11-10 11:13:23 -0600 [Re: [BackupPC-users] Execute 
bash script after each share on backup server]:
> On Fri, Nov 10, 2017 at 10:11 AM, Julian Zielke
> <jzie...@next-level-integration.com> wrote:
> > I???ve written a script which should be run after each processed
> > share of a host.
> >
> > So I???ve tried using:
> > /bin/bash /etc/BackupPC/notify.sh -c $host -s $share -t $type -r
> > $xferOK
> >
> > The log says it is being executed but also:
> >
> > Backup failed on server01 (DumpPostUserCmd returned error status
> > 256)
> >
> > When I run the script using sh -c ? backuppc iot runs fine.
> >
> > So what???s my mistake here?
>
> Your script needs to return an exit code of 0. [...] you can add a
> line 'exit 0' at the end to make backuppc consider it successful regardless.

that was my first thought, too, but there is a bit of confusion in the question.

1. You are talking about running a script after each processed *share*, but
   the error message complains about DumpPostUserCmd, not DumpPostShareCmd.
   The remark about 'exit 0' (and all of what I'm saying) might apply to a
   different script, not your notify.sh, or you are doing something slightly
   different from what you are describing (or misquoting from memory).

2. You omit which BackupPC configuration variable you are setting to which
   value. It appears you might be setting

   $Conf{DumpPostShareCmd} = '/bin/bash /etc/BackupPC/notify.sh -c $host ...';

   but then again, you might be trying the 'bash notify.sh' invocation on the
   command line with the variables $host, $share, $type, $xferOK quoted here
   instead of the actual values for clarity (or secrecy) (or because you are
   actually using shell variables :).

   In any case, I wonder why you are explicitly invoking a shell instead of
   using a "#!/bin/bash" line in notify.sh. With that line (and execute
   permission on notify.sh), things would be more consistent than what you
   are describing above. [There might be valid reasons like noexec mounts
   preventing you from doing so.]

3. Y

Re: [BackupPC-users] Execute bash script after each share on backup server

2017-11-13 Thread Julian Zielke

Hi,

sorry for the confusion. I've tried with both arguments just for debugging 
purposes.

My script used the basename-command, which isn't available during execution so 
I changed that.
Now I get:

Executing DumpPostShareCmd: /bin/bash -c "/etc/BackupPC/notify.sh *arg1* *arg2*"
server01: -c: line 0: unexpected EOF while looking for matching `"'
server01: -c: line 1: syntax error: unexpected end of file

The command is:
/bin/bash -c "/etc/BackupPC/notify.sh $host $share $type $xferOK"

So what's unexpected here? I have to quote the scrit arguments, otherwise bash 
doesn't recognize them.

- Julian

-Ursprüngliche Nachricht-
Von: Holger Parplies [mailto:wb...@parplies.de]
Gesendet: Freitag, 10. November 2017 19:46
An: General list for user discussion, questions and support 
<backuppc-users@lists.sourceforge.net>
Betreff: Re: [BackupPC-users] Execute bash script after each share on backup 
server

Hi,

Les Mikesell wrote on 2017-11-10 11:13:23 -0600 [Re: [BackupPC-users] Execute 
bash script after each share on backup server]:
> On Fri, Nov 10, 2017 at 10:11 AM, Julian Zielke
> <jzie...@next-level-integration.com> wrote:
> > I???ve written a script which should be run after each processed
> > share of a host.
> >
> > So I???ve tried using:
> > /bin/bash /etc/BackupPC/notify.sh -c $host -s $share -t $type -r
> > $xferOK
> >
> > The log says it is being executed but also:
> >
> > Backup failed on server01 (DumpPostUserCmd returned error status
> > 256)
> >
> > When I run the script using sh -c ? backuppc iot runs fine.
> >
> > So what???s my mistake here?
>
> Your script needs to return an exit code of 0. [...] you can add a
> line 'exit 0' at the end to make backuppc consider it successful regardless.

that was my first thought, too, but there is a bit of confusion in the question.

1. You are talking about running a script after each processed *share*, but
   the error message complains about DumpPostUserCmd, not DumpPostShareCmd.
   The remark about 'exit 0' (and all of what I'm saying) might apply to a
   different script, not your notify.sh, or you are doing something slightly
   different from what you are describing (or misquoting from memory).

2. You omit which BackupPC configuration variable you are setting to which
   value. It appears you might be setting

   $Conf{DumpPostShareCmd} = '/bin/bash /etc/BackupPC/notify.sh -c $host ...';

   but then again, you might be trying the 'bash notify.sh' invocation on the
   command line with the variables $host, $share, $type, $xferOK quoted here
   instead of the actual values for clarity (or secrecy) (or because you are
   actually using shell variables :).

   In any case, I wonder why you are explicitly invoking a shell instead of
   using a "#!/bin/bash" line in notify.sh. With that line (and execute
   permission on notify.sh), things would be more consistent than what you
   are describing above. [There might be valid reasons like noexec mounts
   preventing you from doing so.]

3. You say "When I run the script using sh -c ? backuppc it runs fine".
   First observation: 'sh' is not necessarily 'bash'. Debian made a point of
   teaching the world that a while back. When you mean 'bash', you should say
   'bash', and when you say 'sh', you should be sure you aren't using bashisms.
   Second observation: I don't understand the 'backuppc' in there. Did you
   actually mean 'su' instead of 'sh'?

4. You mention "bash notify.sh" vs. "sh -c notify.sh". Note that the semantics
   of

   ./notify.sh
   bash notify.sh
   bash -c notify.sh

   might be subtly different. I'd recommend selecting one version (the order
   says something about my preference; yours may differ), making sure it
   works, and then sticking to it.

   The point being: an "error status 256", if I'm not mistaken, might as well
   be a simple failure to execute the command at all. BackupPC might be
   telling you "I'm about to execute the following command: ..." followed by
   "It didn't work." - without being able to distinguish between "it failed
   to execute" and "it executed but returned a failure". If you want to be
   sure, put something like "echo `date`: here I am >> /tmp/notify.log" at
   the beginning of notify.sh, supposing you don't already have a different
   way of making sure it is really executed (I'm guessing you don't, because
   you say that the log tells you it is being executed, not "I'm getting
   the notification, so I know it is being executed").

   If it's not executed, it's likely about file system permissions (of
   notify.sh or of /etc/BackupPC) or perhaps selinux ...

If you need more help, you'd need to be

Re: [BackupPC-users] Execute bash script after each share on backup server

2017-11-12 Thread Julian Zielke

Ok, Fi finally fixed it.

First of all I for shure know the difference between sh and bash. I just tried 
out different combinations, though my script doesn't make use of and
bash-only syntax.

However: The PATH-Variable is not available when I execute I, so I added an 
export command at the beginning, resulting in my script working right.

The cleaner way would be to use absolute paths to the separate binaries, so 
I'll use /usr/bin/which  to invoke them properly.
Thanks anyway for your help. I'm glad the tool is so well supported by the 
community, although being free and opensource.

- Julian

-Ursprüngliche Nachricht-
Von: Julian Zielke
Gesendet: Montag, 13. November 2017 08:34
An: General list for user discussion, questions and support 
<backuppc-users@lists.sourceforge.net>
Betreff: AW: [BackupPC-users] Execute bash script after each share on backup 
server

Hi,

sorry for the confusion. I've tried with both arguments just for debugging 
purposes.

My script used the basename-command, which isn't available during execution so 
I changed that.
Now I get:

Executing DumpPostShareCmd: /bin/bash -c "/etc/BackupPC/notify.sh *arg1* *arg2*"
server01: -c: line 0: unexpected EOF while looking for matching `"'
server01: -c: line 1: syntax error: unexpected end of file

The command is:
/bin/bash -c "/etc/BackupPC/notify.sh $host $share $type $xferOK"

So what's unexpected here? I have to quote the scrit arguments, otherwise bash 
doesn't recognize them.

- Julian

-Ursprüngliche Nachricht-
Von: Holger Parplies [mailto:wb...@parplies.de]
Gesendet: Freitag, 10. November 2017 19:46
An: General list for user discussion, questions and support 
<backuppc-users@lists.sourceforge.net>
Betreff: Re: [BackupPC-users] Execute bash script after each share on backup 
server

Hi,

Les Mikesell wrote on 2017-11-10 11:13:23 -0600 [Re: [BackupPC-users] Execute 
bash script after each share on backup server]:
> On Fri, Nov 10, 2017 at 10:11 AM, Julian Zielke
> <jzie...@next-level-integration.com> wrote:
> > I???ve written a script which should be run after each processed
> > share of a host.
> >
> > So I???ve tried using:
> > /bin/bash /etc/BackupPC/notify.sh -c $host -s $share -t $type -r
> > $xferOK
> >
> > The log says it is being executed but also:
> >
> > Backup failed on server01 (DumpPostUserCmd returned error status
> > 256)
> >
> > When I run the script using sh -c ? backuppc iot runs fine.
> >
> > So what???s my mistake here?
>
> Your script needs to return an exit code of 0. [...] you can add a
> line 'exit 0' at the end to make backuppc consider it successful regardless.

that was my first thought, too, but there is a bit of confusion in the question.

1. You are talking about running a script after each processed *share*, but
   the error message complains about DumpPostUserCmd, not DumpPostShareCmd.
   The remark about 'exit 0' (and all of what I'm saying) might apply to a
   different script, not your notify.sh, or you are doing something slightly
   different from what you are describing (or misquoting from memory).

2. You omit which BackupPC configuration variable you are setting to which
   value. It appears you might be setting

   $Conf{DumpPostShareCmd} = '/bin/bash /etc/BackupPC/notify.sh -c $host ...';

   but then again, you might be trying the 'bash notify.sh' invocation on the
   command line with the variables $host, $share, $type, $xferOK quoted here
   instead of the actual values for clarity (or secrecy) (or because you are
   actually using shell variables :).

   In any case, I wonder why you are explicitly invoking a shell instead of
   using a "#!/bin/bash" line in notify.sh. With that line (and execute
   permission on notify.sh), things would be more consistent than what you
   are describing above. [There might be valid reasons like noexec mounts
   preventing you from doing so.]

3. You say "When I run the script using sh -c ? backuppc it runs fine".
   First observation: 'sh' is not necessarily 'bash'. Debian made a point of
   teaching the world that a while back. When you mean 'bash', you should say
   'bash', and when you say 'sh', you should be sure you aren't using bashisms.
   Second observation: I don't understand the 'backuppc' in there. Did you
   actually mean 'su' instead of 'sh'?

4. You mention "bash notify.sh" vs. "sh -c notify.sh". Note that the semantics
   of

   ./notify.sh
   bash notify.sh
   bash -c notify.sh

   might be subtly different. I'd recommend selecting one version (the order
   says something about my preference; yours may differ), making sure it
   works, and then sticking to it.

   The point being: an "error status 256", if I'm not mistaken, might as well
   be a simple failure to execute the command at all. BackupPC might be

[BackupPC-users] Execute bash script after each share on backup server

2017-11-10 Thread Julian Zielke

Hi,

I've written a script which should be run after each processed share of a host.
So I've tried using:

/bin/bash /etc/BackupPC/notify.sh -c $host -s $share -t $type -r $xferOK

The log says it is being executed but also:

Backup failed on server01 (DumpPostUserCmd returned error status 256)

When I run the script using sh -c "..." backuppc iot runs fine.

So what's my mistake here?

-  Julian

Wichtiger Hinweis: Der Inhalt dieser E-Mail ist vertraulich und ausschlie?lich 
f?r den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene 
Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie 
bitte, dass jede Form der Kenntnisnahme, Ver?ffentlichung, Vervielf?ltigung 
oder Weitergabe des Inhalts dieser E-Mail unzul?ssig ist. Wir bitten Sie, sich 
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen. Wir m?chten 
Sie au?erdem darauf hinweisen, dass die Kommunikation per E-Mail ?ber das 
Internet unsicher ist, da f?r unberechtigte Dritte grunds?tzlich die 
M?glichkeit der Kenntnisnahme und Manipulation besteht

Important Note: The information contained in this e-mail is confidential. It is 
intended solely for the addressee. Access to this e-mail by anyone else is 
unauthorized. If you are not the intended recipient, any form of disclosure, 
reproduction, distribution or any action taken or refrained from in reliance on 
it, is prohibited and may be unlawful. Please notify the sender immediately. We 
also would like to inform you that communication via e-mail over the internet 
is insecure because third parties may have the possibility to access and 
manipulate e-mails.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Webinterface css broken

2017-11-08 Thread Julian Zielke

Fixed it, my mistake. Apache had wrong root folder set.


  *   Julian

Von: Julian Zielke [mailto:jzie...@next-level-integration.com]
Gesendet: Mittwoch, 8. November 2017 15:44
An: backuppc-users@lists.sourceforge.net
Betreff: [BackupPC-users] Webinterface css broken

Hi,

I've installed the latest version of BackupPC using the SCGI method and the 
interface shows up on apache.

However, my browsers report some code errors in sortable.js files, making the 
GUI looking like html without css design and the content way much under the 
navigation bar.
Chrome reports:

Resource interpreted as Stylesheet but transferred with MIME type text/html: 
"http://server.domain.local/BackupPC_Admin/images/BackupPC_stnd.css;.
sorttable.js:1 Uncaught SyntaxError: Unexpected token <

All images and the js are loaded, so it's not an Apache permission problem, I 
guess.

- Julian


Wichtiger Hinweis: Der Inhalt dieser E-Mail ist vertraulich und ausschließlich 
für den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene 
Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie 
bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung 
oder Weitergabe des Inhalts dieser E-Mail unzulässig ist. Wir bitten Sie, sich 
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen. Wir möchten 
Sie außerdem darauf hinweisen, dass die Kommunikation per E-Mail über das 
Internet unsicher ist, da für unberechtigte Dritte grundsätzlich die 
Möglichkeit der Kenntnisnahme und Manipulation besteht

Important Note: The information contained in this e-mail is confidential. It is 
intended solely for the addressee. Access to this e-mail by anyone else is 
unauthorized. If you are not the intended recipient, any form of disclosure, 
reproduction, distribution or any action taken or refrained from in reliance on 
it, is prohibited and may be unlawful. Please notify the sender immediately. We 
also would like to inform you that communication via e-mail over the internet 
is insecure because third parties may have the possibility to access and 
manipulate e-mails.

Wichtiger Hinweis: Der Inhalt dieser E-Mail ist vertraulich und ausschließlich 
für den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene 
Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie 
bitte, dass jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung 
oder Weitergabe des Inhalts dieser E-Mail unzulässig ist. Wir bitten Sie, sich 
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen. Wir möchten 
Sie außerdem darauf hinweisen, dass die Kommunikation per E-Mail über das 
Internet unsicher ist, da für unberechtigte Dritte grundsätzlich die 
Möglichkeit der Kenntnisnahme und Manipulation besteht

Important Note: The information contained in this e-mail is confidential. It is 
intended solely for the addressee. Access to this e-mail by anyone else is 
unauthorized. If you are not the intended recipient, any form of disclosure, 
reproduction, distribution or any action taken or refrained from in reliance on 
it, is prohibited and may be unlawful. Please notify the sender immediately. We 
also would like to inform you that communication via e-mail over the internet 
is insecure because third parties may have the possibility to access and 
manipulate e-mails.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

[BackupPC-users] Webinterface css broken

2017-11-08 Thread Julian Zielke

Hi,

I've installed the latest version of BackupPC using the SCGI method and the 
interface shows up on apache.

However, my browsers report some code errors in sortable.js files, making the 
GUI looking like html without css design and the content way much under the 
navigation bar.
Chrome reports:

Resource interpreted as Stylesheet but transferred with MIME type text/html: 
"http://server.domain.local/BackupPC_Admin/images/BackupPC_stnd.css;.
sorttable.js:1 Uncaught SyntaxError: Unexpected token <

All images and the js are loaded, so it's not an Apache permission problem, I 
guess.

- Julian


Wichtiger Hinweis: Der Inhalt dieser E-Mail ist vertraulich und ausschlie?lich 
f?r den bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene 
Adressat dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie 
bitte, dass jede Form der Kenntnisnahme, Ver?ffentlichung, Vervielf?ltigung 
oder Weitergabe des Inhalts dieser E-Mail unzul?ssig ist. Wir bitten Sie, sich 
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen. Wir m?chten 
Sie au?erdem darauf hinweisen, dass die Kommunikation per E-Mail ?ber das 
Internet unsicher ist, da f?r unberechtigte Dritte grunds?tzlich die 
M?glichkeit der Kenntnisnahme und Manipulation besteht

Important Note: The information contained in this e-mail is confidential. It is 
intended solely for the addressee. Access to this e-mail by anyone else is 
unauthorized. If you are not the intended recipient, any form of disclosure, 
reproduction, distribution or any action taken or refrained from in reliance on 
it, is prohibited and may be unlawful. Please notify the sender immediately. We 
also would like to inform you that communication via e-mail over the internet 
is insecure because third parties may have the possibility to access and 
manipulate e-mails.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Re: [BackupPC-users] Web Interface Doesn't Work after F27 Upgrade

Re: [BackupPC-users] Web Interface Doesn't Work after F27 Upgrade

Re: [BackupPC-users] Execute bash script after each share on backup server

Re: [BackupPC-users] Execute bash script after each share on backup server

Re: [BackupPC-users] Execute bash script after each share on backup server

[BackupPC-users] Execute bash script after each share on backup server

Re: [BackupPC-users] Webinterface css broken

[BackupPC-users] Webinterface css broken

8 matches

Site Navigation

Mail list logo

Footer information