Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Install Won't Run #88

Open
micksulley opened this issue Jan 19, 2023 · 16 comments
Open

New Install Won't Run #88

micksulley opened this issue Jan 19, 2023 · 16 comments

Comments

@micksulley
Copy link

I've been using PiKrellCam for many years but my system has failed so I wanted to build a new one.
I found that when I ran the install script it failed, an except -

Note, selecting 'php7.3-common' for regex 'php7.3'
Note, selecting 'php7.3-sass' for regex 'php7.3'
Note, selecting 'php-sass' instead of 'php7.3-sass'
Package php7.3-common is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'php7.3-common' has no installation candidate
E: Unable to locate package php7.3-fpm
E: Couldn't find any package by glob 'php7.3-fpm'
E: Couldn't find any package by regex 'php7.3-fpm'

I edited the install file and changed references to php7.3 to just php. The install script now runs without errors, however I still get "Unable to connect" on the web page.
I am running Buster on a Pi3
Any idea how to fix?

@Jimbolaya64
Copy link

Jimbolaya64 commented Jan 19, 2023

Check out issue #87.

@micksulley
Copy link
Author

That doesn't help. I edited the install file to remove the version references for PHP and the install runs fine, or seems to, but I still get "Unable to connect" on the web page.
This is my install -

pi@pi-porch:~/pikrellcam $ ./install-pikrellcam.sh

Set the port for the nginx web server.
If you already have a web server configuration using the default
port 80, you should enter an alternate port for PiKrellCam.
Otherwise you can use the default port 80 or an alternate as you wish.
The port number will be set in: /etc/nginx.sites-available/pikrellcam.
Enter web server port: 

For auto starting at boot, a PiKrellCam start command must be in rc.local.
If you don't start at boot, PiKrellCam can always be started and stopped
from the web page.
Do you want PiKrellCam to be auto started at boot? (yes/no): yes

Enter a password for a web page login for user: pi
Enter a blank entry if you do not want the password login.
Enter password: 

Starting PiKrellCam install...
No packages need to be installed.
./install-pikrellcam.sh: line 194: ./pikrellcam: No such file or directory
Setting install_dir config line in /home/pi/.pikrellcam/pikrellcam.conf:
install_dir /home/pi/pikrellcam
Adding a pikrellcam autostart command to /etc/rc.local:
su pi -c '(sleep 5; /home/pi/pikrellcam/pikrellcam) &'
Adding to /etc/sudoers.d: www-data permission to run pikrellcam as user pi:
Installing /etc/nginx/sites-available/pikrellcam
    nginx web server port: 80
    nginx web server root: /home/pi/pikrellcam/www
A password for the web page is not set.

Install finished.
This install script does not automatically start pikrellcam.
To start pikrellcam, open a browser page to:
    http://your_pi
and click on the "System" panel and then the "Start PiKrellCam" button.
PiKrellCam can also be run from a Pi terminal for testing purposes.
Automatic pikrellcam starting at boot is enabled.


@micksulley
Copy link
Author

Just realised I am running Bullseye, not Buster, don't know if that makes any difference

@micksulley
Copy link
Author

Having investigated and tested some more, I now have PiKrellCam running on a fresh install of Buster. I cannot get it to run on Bullseye, my guess is that it is due to the changed to the camera software in the new release.
Anyone know if PiKrellCam is likely to be upgraded to run with Bullseye?

@AratoArpad
Copy link

Having investigated and tested some more, I now have PiKrellCam running on a fresh install of Buster. I cannot get it to run on Bullseye, my guess is that it is due to the changed to the camera software in the new release. Anyone know if PiKrellCam is likely to be upgraded to run with Bullseye?

Hey,

I was on the same journey as you. I couldn't get it working, same with motioneye, the ribbon cable camera modules don't really cooperate well with the latest release.

It's unlikely that PiKrellCam will get an official update for Bullseye.
If I'm not mistaken, the creator of the project is not with us any more.

@z-noob115
Copy link

micksulley, did you still change php. on the working fresh install? I'm striking out on every attempt

@micksulley
Copy link
Author

micksulley, did you still change php. on the working fresh install? I'm striking out on every attempt

I changed php on the Bullseye install to get PiKrellCam to install at all, but then it didn't work. On Buster it installed and worked without any changes.

@z-noob115
Copy link

thanks! I'll give it another go but my main problem is the home page is jumpy* and will not show any preview. Tried on Buster lite on RPI4 and Zero with same results

@micksulley
Copy link
Author

micksulley, did you still change php. on the working fresh install? I'm striking out on every attempt

I changed php on the Bullseye install to get PiKrellCam to install at all, but then it didn't work. On Buster it installed and worked without any changes.

@micksulley
Copy link
Author

I have seen that when the camera is not detected. If you run
raspistill -o testshot.jpg
can you open testshot.jpg? If not it seems you have a camera problem.

@z-noob115
Copy link

Thanks micksulley! Still have not figured out what i did wrong but have since gotten multiple instances working and doing some fine tuning. Still learning but the only thing i did different is turning off wifi on install image of OS. Dont see how that would make a difference, but I may be wrong.

@fingerprince1
Copy link

Having investigated and tested some more, I now have PiKrellCam running on a fresh install of Buster. I cannot get it to run on Bullseye, my guess is that it is due to the changed to the camera software in the new release. Anyone know if PiKrellCam is likely to be upgraded to run with Bullseye?

Check out the updates of user Lucaji, he seems to keep this software alive

@jsn-0
Copy link

jsn-0 commented Feb 21, 2023

Have you tried enabling the legacy camera stack when running on Bullseye?

This thread has some details on libcamera replacing the old camera stack in Bullseye and how to re-enable the old legacy camera functionality:
https://forums.raspberrypi.com/viewtopic.php?t=323390

Also, reminder, the original developer of this software and owner of this repo passed away in 2021. RIP, Bill.

@kajan001
Copy link

I am not sure bullseye will work but a legacy buster version still works.
check out issues 80 & 82
#82
#80 (comment)

@Whyzanet
Copy link

Whyzanet commented Jun 26, 2023

I have pikrellcam running under bullseye and while it was some time ago I set it up, I have just updated it to the latest software without issues on the RPI3B+ ( Kernel and OS 32 bit ).
IIRC I had to tweak it to look for php7.4 on the install, and enable the legacy camera stack as mentioned above. I didnt have to build anything extra.

simply raspi-config -> Interface Options -> I1 Legacy Camera Enable

Though it is a pity newer camera hardware that will not work in legacy mode, will not work with pikrellcam as a result.
So you will need legacy camera hardware to use legacy mode to then use pikrellcam

@zweistein22
Copy link

Bullseye does not work any more.
Buster 32bit is the latest install where it works.
If interested, here a fork with correct install on buster (and -unneccessary php7.4 install and build from source integrated.
pikrellcam has a very nice feature which is the -coarse- video motion vectors are produced by the video hardware as a by product.
The later libcamera and picamera2 (from bullseye onwards) do not offer that feature any more . This would require a full rewrite of bill's pikrellcam having to drop the nicest feature it has.
Andreas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants