Hi,
Les Mikesell wrote on 2015-10-28 12:56:16 -0500 [Re: [BackupPC-users] Fatal
error (bad version): /sbin/nologin: invalid option]:
> On Wed, Oct 28, 2015 at 12:04 PM, fujisan
> wrote:
> > [...]
> > So this nologin erro message does not seem to come from user backuppc.
>
> Could it be coming f
On Wed, Oct 28, 2015 at 12:04 PM, fujisan
wrote:
> I did change the shell of user backuppc to /bin/bash and I got the exact same
> error message.
> So this nologin erro message does not seem to come from user backuppc.
>
Could it be coming from the remote side via ssh? I don't see why that
woul
I did change the shell of user backuppc to /bin/bash and I got the exact same
error message.
So this nologin erro message does not seem to come from user backuppc.
Fuji
+--
|This was sent by fujisa...@gmail.com via Backup Centra
On Wed, Oct 28, 2015 at 10:45 AM, fujisan
wrote:
> You did not understand, Les.
>
> It is NOT running from the web interface. it IS running from the command line.
> That is my problem.
>
Here is the relevant part of the error message you posted:
Fatal error (bad version): /sbin/nologin: inva
That's part of the BackupPC documentation:
BackupPC User
It is best if BackupPC runs as a special user, eg backuppc, that has
limited privileges. It is preferred that backuppc belongs to a system
administrator group so that sys admin members can browse BackupPC files, edit
the configuration
On Wed, Oct 28, 2015 at 6:34 AM, fujisan
wrote:
> Well, when i do
>
> su backuppc
>
> it says
>
> This account is currently not available.
>
> But that's normal because the shell is set to /sbin/nologin.
>
> Fuji
>
That's probably a smart configuration to protect the backuppc user. If you
need
You did not understand, Les.
It is NOT running from the web interface. it IS running from the command line.
That is my problem.
+--
|This was sent by fujisa...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.co
On Wed, Oct 28, 2015 at 8:34 AM, fujisan
wrote:
> Well, when i do
>
> su backuppc
>
> it says
>
> This account is currently not available.
>
> But that's normal because the shell is set to /sbin/nologin.
>
If you look at your original error message you posted, you'll see that
it comes from /sbin/
Well, when i do
su backuppc
it says
This account is currently not available.
But that's normal because the shell is set to /sbin/nologin.
Fuji
+--
|This was sent by fujisa...@gmail.com via Backup Central.
|Forward SPAM to ab
"ibs/" is the reversed beginning of the error message you've got.
"Fatal error (bad version):" folowed by the text received from the remote end:
> Fatal error (bad version): /sbin/nologin: invalid option -- 'c'
> Usage: nologin [options] Politely refuse a login.
> Options:
> -h, --help disp
On 28.10.15 13:25, fujisan wrote:
>
> Where is that number 1768059695 coming from?
>
I guess you are getting some text from remote machine instead or rsync protocol
message.
DEC -> HEX -> ASCII
1768059695 -> 6962732F -> ibs/
It looks like you have a problem with ssh login.
You changed shell be
I have noticed that when I run the backup from the web UI, I see this line:
Got remote protocol 1768059695
but when i run it on the command line, I see this one:
Got remote protocol 31
That number (31 or 1768059695) is a version number as seen in the file
/usr/lib64/perl5/vendor_perl/File/Rs
12 matches
Mail list logo