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.

Sign up for GitHub

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

Jump to bottom

Latest release bricks my Pi #46

Closed
spenadel opened this issue Apr 20, 2022 · 29 comments
Closed

Latest release bricks my Pi #46

spenadel opened this issue Apr 20, 2022 · 29 comments
Assignees
@taoteh1221
Labels
bug Something isn't working

Comments

@spenadel
Copy link

spenadel commented Apr 20, 2022 •
edited

Hi - I love the ticker. My pi is on Bullseye. When I upgraded yesterday, it trashed my installation and I had to re-image my pi. Have you seen this behavior? I thought I had a full backup image, but apparently don't, so I need to install an earlier version. Do you have a suggestion as to which version I should downgrade to?

Thanks
@taoteh1221
Copy link
Owner

Hello @spenadel sorry to hear this and thanks for the report. What disk image are you using (raspi os, armbian, dietpi, etc), and what pi model? Try a couple versions earlier. I'll attempt to replicate the issue this weekend on my pi3.

@taoteh1221 taoteh1221 self-assigned this Apr 20, 2022
@taoteh1221 taoteh1221 added the bug Something isn't working label Apr 20, 2022
@spenadel
Copy link
Author

This is a pi4 and I would have put raspi on it. Thanks for looking into this. When I tried it again an hour ago, the raspi would not display the desktop on the tft, nor could I ssh or VNC into it, but I could ping it. Does the latest version upgrade the OS, or perhaps reset the ssh and vnc options on the pi? That could explain what I saw.

@taoteh1221
Copy link
Owner

Ok, thanks for the details. I have a pi4 so I'll use that for testing. The latest releases change to using LXDE desktop's autostart feature, instead of a systemd service (this runs bash scripts more reliably for the recent multi-web-browser support feature). There are other changes related to lightdm auto login too, BUT that is only if raspberry pi os is not detected (for armbian etc, as raspi os has auto login on by default).

@taoteh1221
Copy link
Owner

One other thing @spenadel : Are you using 32bit or 64bit disk image? Raspi os now has 64bit disk images, BUT they only just started doing this...may be bugs in 64bit for a few months, unrelated to the ticker app install.

@taoteh1221
Copy link
Owner

When I tried it again an hour ago, the raspi would not display the desktop on the tft, nor could I ssh or VNC into it, but I could ping it.

SSH usually isn't enabled by default, but you can enable network and SSH in the disk image:

https://raw.githubusercontent.com/taoteh1221/Open_Crypto_Tracker/main/DOCUMENTATION-ETC/RASPBERRY-PI/RASPBERRY-PI-HEADLESS-WIFI-SSH.txt

@taoteh1221
Copy link
Owner

That's odd if you're saying that SSH that was already installed by you previously is acting up, unless you have a firewall on there not properly configured. I'm not sure off the top of my head how the ticker could cause this, but I'll check out the auto-installers logic this Saturday. Sorry about this.

@spenadel
Copy link
Author

spenadel commented Apr 21, 2022 via email

@taoteh1221
Copy link
Owner

Ok, thanks for all the feedback. I freed up some time this morning to look into all this. BTW, the main issue with the ticker ever affecting anything would be it's auto-installation script, which sets up starting at boot etc. The ticker itself is just an index.html file opened as a local file by a web browser...not much there that would affect an entire system's stability. If you still have any issues with the portfolio tracker, feel free to open an issue in that repo here and we'll get that fixed too (sounds like it may be a php8 compatibility issue): https://github.com/taoteh1221/Open_Crypto_Tracker/issues

@taoteh1221
Copy link
Owner

I've replicated what may be a similar issue related to the portfolio tracker problem you are having. Looking into it here at this opened issue: taoteh1221/Open_Crypto_Tracker#41

Thanks for the feedback.

@taoteh1221
Copy link
Owner

@spenadel I tested the latest (2022-4-4) 32bit "Raspberry Pi OS with desktop and recommended software" disk image on my pi3 (I won't have access to my pi4 until saturday), and encounter no errors using the ticker auto-installer. Screenshot from 2022-04-21 11-52-33

Run this on the above-mentioned disk image, it uses the latest auto-installation code:

wget --no-cache -O TICKER-INSTALL.bash https://git.io/Jqzjk;chmod +x TICKER-INSTALL.bash;sudo ./TICKER-INSTALL.bash

There is the "edge case" possibility that if you ran the v3.09.4 upgrade a few weeks ago, that could 'brick' your desktop autostart file, as there was a bug I fixed for that 2 weeks ago in v3.09.5:

ccec436

As for replicating the portfolio tracker bug, all I've found so far is a small issue with fresh installs initially showing a blank screen first run (then shows the admin registration page after reloading the app). In config.php at the very top you can enable debugging output to apache's error logs, and open a new issue on the portfolio tracker github repo / paste the log output into the description, to help me debug any continuing issues with that:

https://github.com/taoteh1221/Open_Crypto_Tracker/blob/main/config.php#L18

@taoteh1221
Copy link
Owner

@spenadel Just for clarification that I understand correctly: You are running the LCD screen ticker, AND the web-app portfolio tracker on the same machine, right? That should be fine on a pi3 and higher, so you should be all set on a pi4.

I saw you quoting version numbers for the portfolio tracker here (5.X), while the LCD screen ticker app is only up to v3.X as of now. Just want to make sure I understand which app you are talking about when trying to replicate issues you are having.

@taoteh1221
Copy link
Owner

My reasoning behind having you test with 32bit disk images is that the raspberry pi team has only just started making 64bit images 2 months ago for the first time EVER, so their could be bugs in those packages they may need to work out:

https://www.tomshardware.com/news/raspberry-pi-64-bit-os-released

So we want to rule that out as a possibility. Hope this makes sense.

@taoteh1221
Copy link
Owner

If you read down a bit in that article ( at: https://www.tomshardware.com/news/raspberry-pi-64-bit-os-released )

We asked Hollingworth to explain the current status of Raspberry Pi OS 64-bit and in his email Hollingworth explains that the 64-bit release has "had less test time than the 32-bit build and therefore might have issues we've not found yet. But otherwise it has equal functionality where it is under our control to provide it." This means that for the majority of users, the move will be friction-less. But of course there will be a few teething issues, most likely from specific edge cases. If you find an issue, report it!

@spenadel
Copy link
Author

spenadel commented Apr 21, 2022 via email

@taoteh1221
Copy link
Owner

I ran both apps on the same Pi4. Your version comment made me realize that I may have been installing the incorrect software (portfolio) versus backing down on the screen ticker code.

No worries, we'll figure it out. Keep in mind v5.12.2 and higher (of portfolio app) renames the admin config array (so the old config file is incompatible...old configs are auto-backup 'ed in the same directory during upgrades). Sorry about this, some of the final growing pains optimizing it.

I recommend trying the latest versions of everything on the 32bit disk image. I just did this on a pi3 this morning, with no issues other than this fairly minor one:

taoteh1221/Open_Crypto_Tracker#41

@taoteh1221
Copy link
Owner

FYI @spenadel if you still get login errors on the portfolio tracker, after enabling debugging at top of config.php like I mentioned, run this command in a terminal to see apache error logs in real time:

sudo tail -f /var/log/apache2/error.log

@spenadel
Copy link
Author

spenadel commented Apr 21, 2022 via email

@spenadel
Copy link
Author

spenadel commented Apr 21, 2022 via email

@taoteh1221 taoteh1221 mentioned this issue Apr 21, 2022
Closed
@taoteh1221
Copy link
Owner

I was able to create the admin account using Safari. There could be an add-on in Firefox that’s creating the problem, which I will address. Thank you for your support – I’m good now.

Glad you found a workaround. I'll test admin registration with firefox, and fix any issues I notice. I usually use chrome, so I haven't yet done this:

taoteh1221/Open_Crypto_Tracker#42

Thanks for all the feedback Lee, I appreciate it. 👍

@spenadel
Copy link
Author

spenadel commented Apr 21, 2022 via email

@taoteh1221
Copy link
Owner

Why would I be seeing this log entry: [Thu Apr 21 16:13:37.250907 2022] [access_compat:error] [pid 620:tid 2852045824] [client 166.77.201.16:48634] AH01797: client denied by server configuration: /var/www/html/plugins/htaccess_security_check.dat

That's the app on occasion checking that you have the proper htaccess security settings enabled on the web server. If it was ever NOT denied access to the cache directory via https, then the app would warn you in the interface that you needed to correct it. That's GOOD it's being denied access during it's self-checks. It means your cache directory is NOT accessible via a web address call. It's secure in that way.

@taoteh1221
Copy link
Owner

If you visit https://your.app.install.address/cache you'll see what I mean. You should be denied access.

@taoteh1221
Copy link
Owner

Actually in that particular case: https://your.app.install.address/plugins

That's checked as well for security on occasion.

@taoteh1221
Copy link
Owner

That's the apache error logs, correct?

@spenadel
Copy link
Author

spenadel commented Apr 22, 2022 via email

@taoteh1221
Copy link
Owner

Sorry, I have no idea how to turn off the display other than MAYBE change the ticker to not keep the screen on during a 'do-not-disturb' time. Currently it virtually taps the Ctrl key every 60 seconds via a cron job.

@taoteh1221
Copy link
Owner

You could experiment if you can find this file, then disable the last line by putting a # in front of it:

https://github.com/taoteh1221/Slideshow_Crypto_Ticker/blob/main/bash/cron/keep-screensaver-off.bash#L11

That will disable the ticker from keeping the screen turned on all the time. It really all depends if your screen supports turning off when the screen goes blank, thats a hardware setting as far as I'm aware (not a software setting).

@taoteh1221
Copy link
Owner

@spenadel Thank you for the report on firefox not liking the portfolio tracker admin registration page. I have confirmed this bug, and will have a fix in the next release (v5.14.4): taoteh1221/Open_Crypto_Tracker#42

@taoteh1221
Copy link
Owner

@spenadel The upcoming release of the tracker app (v5.15.4 will be out in a few days) has a fix completed that lets you register / reset the admin account using firefox: taoteh1221/Open_Crypto_Tracker@a18b00c

Thanks very much for the feedback! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@taoteh1221 taoteh1221

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@taoteh1221 @spenadel