Send Motion-user mailing list submissions to
        motion-user@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
        motion-user-requ...@lists.sourceforge.net

You can reach the person managing the list at
        motion-user-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."


Today's Topics:

   1. Missing shared object (David Powell)
   2. Re: Missing shared object (David Powell)


----------------------------------------------------------------------

Message: 1
Date: Fri, 18 Jun 2021 19:22:06 -0500
From: David Powell <da...@depowell.com>
To: Motion discussion list <Motion-user@lists.sourceforge.net>
Subject: [Motion-user] Missing shared object
Message-ID: <5a0581c3-e97b-ec39-86fc-c2e1dc6dd...@depowell.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

I'm still trying to move up from my RPi 3b+ to a 4b for my Motion server.

_*Good Stuff:*_

I've installed Ubuntu 20.04.

I've installed MySQL and I can log into it from various clients.

I've copied over my camera configuration files and my "camera meta-data"
database. After some fiddling, that works well.

I installed Motion using /sudo apt install
./focal_motion_4.3.2-1_arm64.deb/. It seems to be running, meaning that
it's creating movies and snapshots, and it's writing to the motion log.?
I can bring up the Motion web page and "select" (see below) the various
cameras.

_*Not So Good Stuff:*_

I can't see any of the camera feeds.? All of them show a broken image on
the webcontrol page.

If I try to view a camera in a web browser according to the
documentation
<https://motion-project.github.io/motion_config.html#OptDetail_Stream>,
I get no data at all.

For every camera, I get repeated errors in the motion log:

*[7:ml7:gate] [ERR] [DBL] [Jun 18 18:29:19] dbse_init_mysql: Cannot
connect to MySQL database cameras on host localhost with user motion
[7:ml7:gate] [ERR] [DBL] [Jun 18 18:29:19] dbse_init_mysql: MySQL error
was Plugin caching_sha2_password could not be loaded:
/usr/lib/aarch64-linux-gnu/mariadb19/plugin/caching_sha2_password.so:
cannot open shared object file: No such file or directory*

None of the metadata is being entered into the database.

_*Questions:*_

Based on the log entries, it looks to me like this pre-compiled version
of Motion may have been compiled for use with MariaDB instead of MySQL.
Could that be the problem?? The shared object file (and most of that
directory) in the log is definitely not there. Is there some kind of
switch to tell it to use MySQL instead?

Will I need to build Motion from scratch instead of using the
pre-compiled binary?? I wasn't planning to install the toolchains on
this machine.

Thanks, David


-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Fri, 18 Jun 2021 22:45:48 -0500
From: David Powell <da...@depowell.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Missing shared object
Message-ID:
        <17a225fe1f8.279e.ce3d8395e0ae66063e5e142696dac...@depowell.com>
Content-Type: text/plain; charset="us-ascii"; Format="flowed"

Never mind.  I went ahead and built it from source and it's working now.


On June 18, 2021 7:23:45 PM David Powell <da...@depowell.com> wrote:
> I'm still trying to move up from my RPi 3b+ to a 4b for my Motion server.
>
> Good Stuff:
>
>
> I've installed Ubuntu 20.04.
>
>
> I've installed MySQL and I can log into it from various clients.
>
> I've copied over my camera configuration files and my "camera meta-data" 
> database. After some fiddling, that works well.
>
>
> I installed Motion using sudo apt install ./focal_motion_4.3.2-1_arm64.deb. 
> It seems to be running, meaning that it's creating movies and snapshots, 
> and it's writing to the motion log.  I can bring up the Motion web page and 
> "select" (see below) the various cameras.
>
> Not So Good Stuff:
>
>
> I can't see any of the camera feeds.  All of them show a broken image on 
> the webcontrol page.
>
>
> If I try to view a camera in a web browser according to the documentation, 
> I get no data at all.
>
> For every camera, I get repeated errors in the motion log:
>
> [7:ml7:gate] [ERR] [DBL] [Jun 18 18:29:19] dbse_init_mysql: Cannot connect 
> to MySQL database cameras on host localhost with user motion
> [7:ml7:gate] [ERR] [DBL] [Jun 18 18:29:19] dbse_init_mysql: MySQL error was 
> Plugin caching_sha2_password could not be loaded: 
> /usr/lib/aarch64-linux-gnu/mariadb19/plugin/caching_sha2_password.so: 
> cannot open shared object file: No such file or directory
>
> None of the metadata is being entered into the database.
>
>
> Questions:
>
>
> Based on the log entries, it looks to me like this pre-compiled version of 
> Motion may have been compiled for use with MariaDB instead of MySQL. Could 
> that be the problem?  The shared object file (and most of that directory) 
> in the log is definitely not there. Is there some kind of switch to tell it 
> to use MySQL instead?
>
>
> Will I need to build Motion from scratch instead of using the pre-compiled 
> binary?  I wasn't planning to install the toolchains on this machine.
>
>
> Thanks, David
>
>
>
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user

-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------



------------------------------

Subject: Digest Footer

_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user


------------------------------

End of Motion-user Digest, Vol 180, Issue 11
********************************************

Reply via email to