date:20200521

Re: [Bacula-users] Baculum Install on Centos 7

2020-05-21 Thread Marcin Haba

Hello Jeff,

How is it possible that in repository are packages with suffix el7 and
your packages have fc31? Please look at the repository address:

http://bacula.org/downloads/baculum/stable/centos

There isn't any packages marked 'fc31' and your packages have it:

rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by baculum-api-9.6.3-1.fc31.noarch
rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by
baculum-api-httpd-9.6.3-1.fc31.noarch
rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by
baculum-common-9.6.3-1.fc31.noarch

I don't know how it could be possible.

Best regards,
Marcin Haba (gani)

On Fri, 22 May 2020 at 00:06, Jeff Thomas  wrote:
>
> I'm using the following repos.d file:
>
> [root@costello jrthomas]# cat /etc/yum.repos.d/baculum.repo
> [baculumrepo]
> name=Baculum CentOS repository
> baseurl=http://bacula.org/downloads/baculum/stable/centos
> gpgcheck=1
> enabled=1
>
>
>
>
> On Thu, May 21, 2020 at 4:40 PM Marcin Haba  wrote:
>>
>> Hello Jeff,
>>
>> It looks you are trying to install Fedora 31 packages on CentOS.
>>
>> I would propose to use Baculum packages dedicated for CentOS 7. You
>> can take them from here:
>>
>> https://www.bacula.org/9.6.x-manuals/en/console/Baculum_API_Web_GUI_Tools.html#SECTION0034
>>
>> Best regards,
>> Marcin Haba (gani)
>>
>> On Thu, 21 May 2020 at 23:04, Jeff Thomas  wrote:
>> >
>> > I'm following the instructions to the letter and then 'WHAM!'
>> >
>> > Running transaction check
>> > ERROR You need to update rpm to handle:
>> > rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by 
>> > baculum-api-9.6.3-1.fc31.noarch
>> > rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by 
>> > baculum-api-httpd-9.6.3-1.fc31.noarch
>> > rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by 
>> > baculum-common-9.6.3-1.fc31.noarch
>> >
>> > I don't get it.   From what I can tell zstd enabled RPM is a fiction for 
>> > some future release of Centos 8?
>> >
>> > I'd appreciate some help.
>> >
>> > Thanks!
>> >
>> >
>> > ___
>> > Bacula-users mailing list
>> > Bacula-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>>
>>
>> --
>> "Greater love hath no man than this, that a man lay down his life for
>> his friends." Jesus Christ
>>
>> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
>> za przyjaciół swoich." Jezus Chrystus



-- 
"Greater love hath no man than this, that a man lay down his life for
his friends." Jesus Christ

"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
za przyjaciół swoich." Jezus Chrystus


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

2020-05-21 Thread r0...@nxlplyx.com

Hi Martin,

Thank you.  But I got the same result.

---

$ make CFLAGS=-I/usr/include/x86_64-linux-gnu  deb

make: *** No rule to make target 'curl/curl.h', needed by
'build/obj/acl.do'.  Stop.

---

and just for consistency, I ran Radoslaw's command and got the results
below:

=

$ dpkg -S curl.h
libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h

=


Well, if anyone can help I'd appreciate it.

Regards,

Al.


On 5/21/20 12:55 PM, Martin Simmons wrote:
> If you were trying to set CFLAGS to -I/usr/include/x86_64-linux-gnu then you
> must remove the space after CFLAGS=, i.e. use
>
> make CFLAGS=-I/usr/include/x86_64-linux-gnu deb
>
> __Martin
>
>
>> On Wed, 20 May 2020 20:40:23 -0400, r0002@nxlplyx com said:
>> Hi Radoslaw,
>>
>> I still get the same results.  Judging by the error message, I am
>> guessing that it finds them, but doesn't know what to do with them
>> because there is no rule for them.
>>
>> ===
>>
>> $ make CFLAGS= -I/usr/include/x86_64-linux-gnu  deb
>>
>> make: *** No rule to make target 'curl/curl.h', needed by
>> 'build/obj/acl.do'.  Stop.
>>
>> ===
>>
>> Thanks for the attempt to help.
>>
>> Has anyone actually gotten the S3 module  to work in Ubuntu 18.04 that
>> can give a hand?
>>
>> Regards,
>>
>> Al
>>
>> On 5/20/20 4:38 AM, Radosław Korzeniewski wrote:
>>> Hello,
>>>
>>> Hi Radoslaw,
>>>
>>> I believe I have tried every kind of library combination, to no avail.
>>>
>>> Your compilation requires a following header file to be
>>> available: curl/curl.h
>>> In my development machine (Debian) it is available with the following
>>> package:
>>> # dpkg -S curl.h
>>> libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h
>>>
>>> So, I suggested that it should be available in a similar package in
>>> Ubuntu (and it seems it is the exact package).
>>> You have to check where this header file is installed and what package
>>> provides it. If it does not fit then you should alter your compilation
>>> flags, i.e. CFLAGS and CPPFLAGS to provide a correct header file location.
>>>
>>> I hope it helps.
>>>
>>> Radek
>>> -- 
>>> Radosław Korzeniewski
>>> rados...@korzeniewski.net 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Baculum Install on Centos 7

2020-05-21 Thread Jeff Thomas

I'm using the following repos.d file:

[root@costello jrthomas]# cat /etc/yum.repos.d/baculum.repo
[baculumrepo]
name=Baculum CentOS repository
baseurl=http://bacula.org/downloads/baculum/stable/centos
gpgcheck=1
enabled=1




On Thu, May 21, 2020 at 4:40 PM Marcin Haba  wrote:

> Hello Jeff,
>
> It looks you are trying to install Fedora 31 packages on CentOS.
>
> I would propose to use Baculum packages dedicated for CentOS 7. You
> can take them from here:
>
>
> https://www.bacula.org/9.6.x-manuals/en/console/Baculum_API_Web_GUI_Tools.html#SECTION0034
>
> Best regards,
> Marcin Haba (gani)
>
> On Thu, 21 May 2020 at 23:04, Jeff Thomas  wrote:
> >
> > I'm following the instructions to the letter and then 'WHAM!'
> >
> > Running transaction check
> > ERROR You need to update rpm to handle:
> > rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by
> baculum-api-9.6.3-1.fc31.noarch
> > rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by
> baculum-api-httpd-9.6.3-1.fc31.noarch
> > rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by
> baculum-common-9.6.3-1.fc31.noarch
> >
> > I don't get it.   From what I can tell zstd enabled RPM is a fiction for
> some future release of Centos 8?
> >
> > I'd appreciate some help.
> >
> > Thanks!
> >
> >
> > ___
> > Bacula-users mailing list
> > Bacula-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
>
> --
> "Greater love hath no man than this, that a man lay down his life for
> his friends." Jesus Christ
>
> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
> za przyjaciół swoich." Jezus Chrystus
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Baculum Install on Centos 7

2020-05-21 Thread Marcin Haba

Hello Jeff,

It looks you are trying to install Fedora 31 packages on CentOS.

I would propose to use Baculum packages dedicated for CentOS 7. You
can take them from here:

https://www.bacula.org/9.6.x-manuals/en/console/Baculum_API_Web_GUI_Tools.html#SECTION0034

Best regards,
Marcin Haba (gani)

On Thu, 21 May 2020 at 23:04, Jeff Thomas  wrote:
>
> I'm following the instructions to the letter and then 'WHAM!'
>
> Running transaction check
> ERROR You need to update rpm to handle:
> rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by baculum-api-9.6.3-1.fc31.noarch
> rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by 
> baculum-api-httpd-9.6.3-1.fc31.noarch
> rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by 
> baculum-common-9.6.3-1.fc31.noarch
>
> I don't get it.   From what I can tell zstd enabled RPM is a fiction for some 
> future release of Centos 8?
>
> I'd appreciate some help.
>
> Thanks!
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users



-- 
"Greater love hath no man than this, that a man lay down his life for
his friends." Jesus Christ

"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
za przyjaciół swoich." Jezus Chrystus


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Baculum-Web Install Problem (Debian Buster)

2020-05-21 Thread Marcin Haba

Hello Chris,

Yes, there exist Baculum packages for Debian Buster. Information about
repositories you can find in the Baculum documentation chapter here:

https://www.bacula.org/9.6.x-manuals/en/console/Baculum_API_Web_GUI_Tools.html#SECTION00351000

Best regards,
Marcin Haba (gani)

On Thu, 21 May 2020 at 23:04, Chris Wilkinson  wrote:
>
> Hello Marcin
>
> Yes that is true, PHP came from the Buster repo.
>
> Is there Baculum in the Buster repo, I couldn't find one?
>
> As to why Stretch and Buster PHP'S are different, I don't really have any 
> idea. I don't see what I could do about that.
>
> Is anybody running Baculum in Buster?
>
> Regards
> Chris Wilkinson
>
> On Thu, 21 May 2020, 9:44 p.m. Marcin Haba,  wrote:
>>
>> Hello Chris,
>>
>> You use PHP not from Stretch repository. It looks that your PHP
>> interpreter doesn't match PHP modules. Maybe they were prepared in
>> different environment? At least pdo_mysql couldn't be loaded.
>>
>> In any cases it is PHP related problem. I would propose to verify from
>> where come modules and interpreter and why they are different.
>>
>> I hope it helps.
>>
>> Best regards,
>> Marcin Haba (gani)
>>
>> On Thu, 21 May 2020 at 21:53, Chris Wilkinson  wrote:
>> >
>> > I upgraded Baculum to 9.6.3 from the Stretch repository. Installation went 
>> > OK until I opened the Web client and got the following error in an error 
>> > box as soon as any data request was made, e.g. list job history. Bacula is 
>> > v9.4.2.
>> >
>> > Error code: 100
>> >
>> > Message: Problem with connection to remote host. cURL error 0: . 
>> > {"output":[],"error":0}
>> >
>> > Prado\Exceptions\TPhpFatalErrorException
>> >
>> > Description
>> >
>> > [Core Warning] PHP Startup: Unable to load dynamic library 'pdo_mysql' 
>> > (tried: /usr/lib/php/20180731/pdo_mysql (/usr/lib/php/20180731/pdo_mysql: 
>> > cannot open shared object file: No such file or directory), 
>> > /usr/lib/php/20180731/pdo_mysql.so (/usr/lib/php/20180731/pdo_mysql.so: 
>> > undefined symbol: mysqlnd_allocator)) (@line 0 in file Unknown).
>> >
>> > Source File
>> >
>> > /usr/share/baculum/htdocs/framework/pradosoft/prado/framework/PradoBase.php
>> >  (193)
>> >
>> > 0182:  * PHP shutdown function used to catch fatal errors.
>> > 0183:  * This method should be registered as PHP error handler using
>> > 0184:  * {@link register_shutdown_function}. The method throws an 
>> > exception that
>> > 0185:  * contains the error information.
>> > 0186:  */
>> > 0187: public static function phpFatalErrorHandler()
>> > 0188: {
>> > 0189: $error = error_get_last();
>> > 0190: if ($error &&
>> > 0191: TPhpErrorException::isFatalError($error) &&
>> > 0192: error_reporting() & $error['type']) {
>> > 0193: self::exceptionHandler(new 
>> > TPhpFatalErrorException($error['type'], $error['message'], $error['file'], 
>> > $error['line']));
>> > 0194: }
>> > 0195: }
>> > 0196:
>> > 0197: /**
>> > 0198:  * Default exception handler.
>> > 0199:  * This method should be registered as default exception handler 
>> > using
>> > 0200:  * {@link set_exception_handler}. The method tries to use the 
>> > errorhandler
>> > 0201:  * module of the Prado application to handle the exception.
>> > 0202:  * If the application or the module does not exist, it simply 
>> > echoes the
>> > 0203:  * exception.
>> > 0204:  * @param Exception $exception exception that is not caught
>> > 0205:  */
>> >
>> > Stack Trace
>> >
>> > #0 [internal function]: Prado\PradoBase::phpFatalErrorHandler()
>> > #1 {main}
>> >
>> > 2020-05-21 17:04 Apache/2.4.38 (Debian) PRADO/4.0.1
>> >
>> >
>> > The missing file /usr/lib/php/20180731/pdo_mysql.so noted above is 
>> > actually present.
>> >
>> > -$ ls /usr/lib/php/20180731/
>> > apc.so   ftp.so   mysqli.so  redis.so  sysvshm.so
>> > apcu.so  gd.somysqlnd.so shmop.so  tokenizer.so
>> > bcmath.sogettext.so   opcache.so simplexml.so  wddx.so
>> > calendar.so  iconv.so “pdo_mysql.so"   smbclient.so  xmlreader.so
>> > ctype.so igbinary.so  pdo.so sockets.soxml.so
>> > curl.so  imagick.so   pdo_sqlite.so  sqlite3.soxmlwriter.so
>> > dom.so   intl.so  phar.sossh2.so   xsl.so
>> > exif.so  json.so  posix.so   sysvmsg.sozip.so
>> > fileinfo.so  mbstring.so  readline.sosysvsem.so
>> >
>> > Would be glad of any pointers to correct this.
>> >
>> > Best
>> > Chris Wilkinson
>> > ___
>> > Bacula-users mailing list
>> > Bacula-users@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>>
>>
>> --
>> "Greater love hath no man than this, that a man lay down his life for
>> his friends." Jesus Christ
>>
>> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
>> za przyjaciół swoich." Jezus Chrystus



--

Re: [Bacula-users] Baculum-Web Install Problem (Debian Buster)

2020-05-21 Thread Chris Wilkinson

Hello Marcin

Yes that is true, PHP came from the Buster repo.

Is there Baculum in the Buster repo, I couldn't find one?

As to why Stretch and Buster PHP'S are different, I don't really have any
idea. I don't see what I could do about that.

Is anybody running Baculum in Buster?

Regards
Chris Wilkinson

On Thu, 21 May 2020, 9:44 p.m. Marcin Haba,  wrote:

> Hello Chris,
>
> You use PHP not from Stretch repository. It looks that your PHP
> interpreter doesn't match PHP modules. Maybe they were prepared in
> different environment? At least pdo_mysql couldn't be loaded.
>
> In any cases it is PHP related problem. I would propose to verify from
> where come modules and interpreter and why they are different.
>
> I hope it helps.
>
> Best regards,
> Marcin Haba (gani)
>
> On Thu, 21 May 2020 at 21:53, Chris Wilkinson 
> wrote:
> >
> > I upgraded Baculum to 9.6.3 from the Stretch repository. Installation
> went OK until I opened the Web client and got the following error in an
> error box as soon as any data request was made, e.g. list job history.
> Bacula is v9.4.2.
> >
> > Error code: 100
> >
> > Message: Problem with connection to remote host. cURL error 0: .
> {"output":[],"error":0}
> >
> > Prado\Exceptions\TPhpFatalErrorException
> >
> > Description
> >
> > [Core Warning] PHP Startup: Unable to load dynamic library 'pdo_mysql'
> (tried: /usr/lib/php/20180731/pdo_mysql (/usr/lib/php/20180731/pdo_mysql:
> cannot open shared object file: No such file or directory),
> /usr/lib/php/20180731/pdo_mysql.so (/usr/lib/php/20180731/pdo_mysql.so:
> undefined symbol: mysqlnd_allocator)) (@line 0 in file Unknown).
> >
> > Source File
> >
> >
> /usr/share/baculum/htdocs/framework/pradosoft/prado/framework/PradoBase.php
> (193)
> >
> > 0182:  * PHP shutdown function used to catch fatal errors.
> > 0183:  * This method should be registered as PHP error handler using
> > 0184:  * {@link register_shutdown_function}. The method throws an
> exception that
> > 0185:  * contains the error information.
> > 0186:  */
> > 0187: public static function phpFatalErrorHandler()
> > 0188: {
> > 0189: $error = error_get_last();
> > 0190: if ($error &&
> > 0191: TPhpErrorException::isFatalError($error) &&
> > 0192: error_reporting() & $error['type']) {
> > 0193: self::exceptionHandler(new
> TPhpFatalErrorException($error['type'], $error['message'], $error['file'],
> $error['line']));
> > 0194: }
> > 0195: }
> > 0196:
> > 0197: /**
> > 0198:  * Default exception handler.
> > 0199:  * This method should be registered as default exception
> handler using
> > 0200:  * {@link set_exception_handler}. The method tries to use the
> errorhandler
> > 0201:  * module of the Prado application to handle the exception.
> > 0202:  * If the application or the module does not exist, it simply
> echoes the
> > 0203:  * exception.
> > 0204:  * @param Exception $exception exception that is not caught
> > 0205:  */
> >
> > Stack Trace
> >
> > #0 [internal function]: Prado\PradoBase::phpFatalErrorHandler()
> > #1 {main}
> >
> > 2020-05-21 17:04 Apache/2.4.38 (Debian) PRADO/4.0.1
> >
> >
> > The missing file /usr/lib/php/20180731/pdo_mysql.so noted above is
> actually present.
> >
> > -$ ls /usr/lib/php/20180731/
> > apc.so   ftp.so   mysqli.so  redis.so  sysvshm.so
> > apcu.so  gd.somysqlnd.so shmop.so  tokenizer.so
> > bcmath.sogettext.so   opcache.so simplexml.so  wddx.so
> > calendar.so  iconv.so “pdo_mysql.so"   smbclient.so  xmlreader.so
> > ctype.so igbinary.so  pdo.so sockets.soxml.so
> > curl.so  imagick.so   pdo_sqlite.so  sqlite3.soxmlwriter.so
> > dom.so   intl.so  phar.sossh2.so   xsl.so
> > exif.so  json.so  posix.so   sysvmsg.sozip.so
> > fileinfo.so  mbstring.so  readline.sosysvsem.so
> >
> > Would be glad of any pointers to correct this.
> >
> > Best
> > Chris Wilkinson
> > ___
> > Bacula-users mailing list
> > Bacula-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bacula-users
>
>
>
> --
> "Greater love hath no man than this, that a man lay down his life for
> his friends." Jesus Christ
>
> "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
> za przyjaciół swoich." Jezus Chrystus
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Baculum Install on Centos 7

2020-05-21 Thread Jeff Thomas

I'm following the instructions to the letter and then 'WHAM!'

Running transaction check
ERROR You need to update rpm to handle:
rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by
baculum-api-9.6.3-1.fc31.noarch
rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by
baculum-api-httpd-9.6.3-1.fc31.noarch
rpmlib(PayloadIsZstd) <= 5.4.18-1 is needed by
baculum-common-9.6.3-1.fc31.noarch

I don't get it.   From what I can tell zstd enabled RPM is a fiction for
some future release of Centos 8?

I'd appreciate some help.

Thanks!
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Baculum-Web Install Problem (Debian Buster)

2020-05-21 Thread Marcin Haba

Hello Chris,

You use PHP not from Stretch repository. It looks that your PHP
interpreter doesn't match PHP modules. Maybe they were prepared in
different environment? At least pdo_mysql couldn't be loaded.

In any cases it is PHP related problem. I would propose to verify from
where come modules and interpreter and why they are different.

I hope it helps.

Best regards,
Marcin Haba (gani)

On Thu, 21 May 2020 at 21:53, Chris Wilkinson  wrote:
>
> I upgraded Baculum to 9.6.3 from the Stretch repository. Installation went OK 
> until I opened the Web client and got the following error in an error box as 
> soon as any data request was made, e.g. list job history. Bacula is v9.4.2.
>
> Error code: 100
>
> Message: Problem with connection to remote host. cURL error 0: . 
> {"output":[],"error":0}
>
> Prado\Exceptions\TPhpFatalErrorException
>
> Description
>
> [Core Warning] PHP Startup: Unable to load dynamic library 'pdo_mysql' 
> (tried: /usr/lib/php/20180731/pdo_mysql (/usr/lib/php/20180731/pdo_mysql: 
> cannot open shared object file: No such file or directory), 
> /usr/lib/php/20180731/pdo_mysql.so (/usr/lib/php/20180731/pdo_mysql.so: 
> undefined symbol: mysqlnd_allocator)) (@line 0 in file Unknown).
>
> Source File
>
> /usr/share/baculum/htdocs/framework/pradosoft/prado/framework/PradoBase.php 
> (193)
>
> 0182:  * PHP shutdown function used to catch fatal errors.
> 0183:  * This method should be registered as PHP error handler using
> 0184:  * {@link register_shutdown_function}. The method throws an 
> exception that
> 0185:  * contains the error information.
> 0186:  */
> 0187: public static function phpFatalErrorHandler()
> 0188: {
> 0189: $error = error_get_last();
> 0190: if ($error &&
> 0191: TPhpErrorException::isFatalError($error) &&
> 0192: error_reporting() & $error['type']) {
> 0193: self::exceptionHandler(new 
> TPhpFatalErrorException($error['type'], $error['message'], $error['file'], 
> $error['line']));
> 0194: }
> 0195: }
> 0196:
> 0197: /**
> 0198:  * Default exception handler.
> 0199:  * This method should be registered as default exception handler 
> using
> 0200:  * {@link set_exception_handler}. The method tries to use the 
> errorhandler
> 0201:  * module of the Prado application to handle the exception.
> 0202:  * If the application or the module does not exist, it simply 
> echoes the
> 0203:  * exception.
> 0204:  * @param Exception $exception exception that is not caught
> 0205:  */
>
> Stack Trace
>
> #0 [internal function]: Prado\PradoBase::phpFatalErrorHandler()
> #1 {main}
>
> 2020-05-21 17:04 Apache/2.4.38 (Debian) PRADO/4.0.1
>
>
> The missing file /usr/lib/php/20180731/pdo_mysql.so noted above is actually 
> present.
>
> -$ ls /usr/lib/php/20180731/
> apc.so   ftp.so   mysqli.so  redis.so  sysvshm.so
> apcu.so  gd.somysqlnd.so shmop.so  tokenizer.so
> bcmath.sogettext.so   opcache.so simplexml.so  wddx.so
> calendar.so  iconv.so “pdo_mysql.so"   smbclient.so  xmlreader.so
> ctype.so igbinary.so  pdo.so sockets.soxml.so
> curl.so  imagick.so   pdo_sqlite.so  sqlite3.soxmlwriter.so
> dom.so   intl.so  phar.sossh2.so   xsl.so
> exif.so  json.so  posix.so   sysvmsg.sozip.so
> fileinfo.so  mbstring.so  readline.sosysvsem.so
>
> Would be glad of any pointers to correct this.
>
> Best
> Chris Wilkinson
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users



-- 
"Greater love hath no man than this, that a man lay down his life for
his friends." Jesus Christ

"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
za przyjaciół swoich." Jezus Chrystus


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Baculum-Web Install Problem (Debian Buster)

2020-05-21 Thread Chris Wilkinson

I upgraded Baculum to 9.6.3 from the Stretch repository. Installation went
OK until I opened the Web client and got the following error in an error
box as soon as any data request was made, e.g. list job history. Bacula is
v9.4.2.

*Error code:* 100

*Message:* Problem with connection to remote host. cURL error 0: .
{"output":[],"error":0}
Prado\Exceptions\TPhpFatalErrorException Description

[Core Warning] PHP Startup: Unable to load dynamic library 'pdo_mysql'
(tried: /usr/lib/php/20180731/pdo_mysql (/usr/lib/php/20180731/pdo_mysql:
cannot open shared object file: No such file or directory),
/usr/lib/php/20180731/pdo_mysql.so (/usr/lib/php/20180731/pdo_mysql.so:
undefined symbol: mysqlnd_allocator)) (@line 0 in file Unknown).
Source File

/usr/share/baculum/htdocs/framework/pradosoft/prado/framework/PradoBase.php
(193)

0182:  * PHP shutdown function used to catch fatal errors.
0183:  * This method should be registered as PHP error handler using
0184:  * {@link register_shutdown_function}. The method throws an
exception that
0185:  * contains the error information.
0186:  */
0187: public static function phpFatalErrorHandler()
0188: {
0189: $error = error_get_last();
0190: if ($error &&
0191: TPhpErrorException::isFatalError($error) &&
0192: error_reporting() & $error['type']) {
0193: self::exceptionHandler(new
TPhpFatalErrorException($error['type'], $error['message'],
$error['file'], $error['line']));
0194: }
0195: }
0196:
0197: /**
0198:  * Default exception handler.
0199:  * This method should be registered as default exception handler using
0200:  * {@link set_exception_handler}. The method tries to use
the errorhandler
0201:  * module of the Prado application to handle the exception.
0202:  * If the application or the module does not exist, it
simply echoes the
0203:  * exception.
0204:  * @param Exception $exception exception that is not caught
0205:  */


Stack Trace

#0 [internal function]: Prado\PradoBase::phpFatalErrorHandler()
#1 {main}

2020-05-21 17:04 Apache/2.4.38 (Debian) PRADO
/4.0.1


The missing file /usr/lib/php/20180731/pdo_mysql.so noted above is actually
present.

-$ ls /usr/lib/php/20180731/
apc.so   ftp.so   mysqli.so  redis.so  sysvshm.so
apcu.so  gd.somysqlnd.so shmop.so  tokenizer.so
bcmath.sogettext.so   opcache.so simplexml.so  wddx.so
calendar.so  iconv.so “pdo_mysql.so"   smbclient.so  xmlreader.so
ctype.so igbinary.so  pdo.so sockets.soxml.so
curl.so  imagick.so   pdo_sqlite.so  sqlite3.soxmlwriter.so
dom.so   intl.so  phar.sossh2.so   xsl.so
exif.so  json.so  posix.so   sysvmsg.sozip.so
fileinfo.so  mbstring.so  readline.sosysvsem.so

Would be glad of any pointers to correct this.

Best
Chris Wilkinson
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

2020-05-21 Thread Martin Simmons

If you were trying to set CFLAGS to -I/usr/include/x86_64-linux-gnu then you
must remove the space after CFLAGS=, i.e. use

make CFLAGS=-I/usr/include/x86_64-linux-gnu deb

__Martin


> On Wed, 20 May 2020 20:40:23 -0400, r0002@nxlplyx com said:
> 
> Hi Radoslaw,
> 
> I still get the same results.  Judging by the error message, I am
> guessing that it finds them, but doesn't know what to do with them
> because there is no rule for them.
> 
> ===
> 
> $ make CFLAGS= -I/usr/include/x86_64-linux-gnu  deb
> 
> make: *** No rule to make target 'curl/curl.h', needed by
> 'build/obj/acl.do'.  Stop.
> 
> ===
> 
> Thanks for the attempt to help.
> 
> Has anyone actually gotten the S3 module  to work in Ubuntu 18.04 that
> can give a hand?
> 
> Regards,
> 
> Al
> 
> On 5/20/20 4:38 AM, Radosław Korzeniewski wrote:
> > Hello,
> >
> > Hi Radoslaw,
> >
> > I believe I have tried every kind of library combination, to no avail.
> >
> > Your compilation requires a following header file to be
> > available: curl/curl.h
> > In my development machine (Debian) it is available with the following
> > package:
> > # dpkg -S curl.h
> > libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h
> >
> > So, I suggested that it should be available in a similar package in
> > Ubuntu (and it seems it is the exact package).
> > You have to check where this header file is installed and what package
> > provides it. If it does not fit then you should alter your compilation
> > flags, i.e. CFLAGS and CPPFLAGS to provide a correct header file location.
> >
> > I hope it helps.
> >
> > Radek
> > -- 
> > Radosław Korzeniewski
> > rados...@korzeniewski.net 
> 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Baculum Install on Centos 7

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

Re: [Bacula-users] Baculum Install on Centos 7

Re: [Bacula-users] Baculum Install on Centos 7

Re: [Bacula-users] Baculum-Web Install Problem (Debian Buster)

Re: [Bacula-users] Baculum-Web Install Problem (Debian Buster)

[Bacula-users] Baculum Install on Centos 7

Re: [Bacula-users] Baculum-Web Install Problem (Debian Buster)

[Bacula-users] Baculum-Web Install Problem (Debian Buster)

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

10 matches

Site Navigation

Mail list logo

Footer information