Thanks!
I just upgrade 5.5.38 to 5.6.37, turn to be OK now.
Not sure what to say but when I did cat /proc/version it did show that version of Red Hat.
If php 7.0 does not have this issue is it the version of PGSQL that is causing the issue?
that’s not how you get an RHEL release name / version.
no, it’s not possible, although you can run into other issues.
what’s more likely is that you either don’t have php 7.0 or have multiple php versions installed. or you have a different problem.
Is there a way to rollback last nights changes? I’d like to do this until I can look into this some more and get on a supported version of PGSQL.
Thanks
yes, just pick an older changeset id in git log and use git checkout. for example git checkout c3d57017d
when you’re ready use git checkout master to go back on trunk
Bugger. I’ve been bitten as well.
$ ttrss-bug-report
tt-rss version (including git commit id):
# git rev-parse --verify HEAD
eb43d9f4a8a8609b7f30ef4e2add425b9c91fe00
Platform (i.e. Linux distro, PHP, PostgreSQL, etc) versions:
# cat /etc/issue
CentOS release 6.9 (Final)
Kernel \r on an \m# uname -a
Linux server.onlinehome-server.info 2.6.32-042stab127.2 #1 SMP Thu Jan 4 16:41:44 MSK 2018 x86_64 x86_64 x86_64 GNU/Linux
# php --version
PHP 5.5.38 (cli) (built: Mar 1 2018 11:12:35)
Copyright (c) 1997-2015 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2015 Zend Technologies
# mysql --version
mysql Ver 14.14 Distrib 5.5.60, for Linux (x86_64) using readline 5.1
Off to see about updating PHP I suppose…
Edit: Upgraded php to 5.6 - I’m sorted.
holy shit, php 5.5 point releases lasted well into 2016. php may be an arguably shitty language but they do support their stuff.
e:
this needs to be a thing
I seem to have really screwed the pooch now. Now when I try and refresh TT-RSS I get the below error. Odd that I did not see this before the update last night.
PHP version 5.6.0 or newer required.
I’ll have work on this later.
yes, latest update to tt-rss finally enforces required php version. looks like you actually don’t have php 7.0 (or you’re not really using it).
$ cat /usr/local/bin/ttrss-bug-report
#!/bin/bash
RED="\x1b[31m"
GREEN="\x1b[32m"
RESET="\x1b[m"
function run(){
echo "# $@"
$@ | anonymise
}
echo -e "${GREEN}"
cat << EOF
# tt-rss version (including git commit id):
\`\`\`
$( run git rev-parse --verify HEAD )
\`\`\`
# Platform (i.e. Linux distro, PHP, PostgreSQL, etc) versions:
\`\`\`
$( run cat /etc/issue )
$( run uname -a )
$( run php --version )
$( run mysql --version )
\`\`\`
EOF
echo -e "${RESET}"
And (change where appropriate)
$ cat /usr/local/bin/anonymise
#!/bin/bash
sed -ue "s/my.site.name/mysite.example.com/g" | \
sed -ue "s/my.site.ip.address/<server ip address>/g" | \
sed -ue "s/my.home.ip.address/<my ip address>/g" | \
sed -ue "s/my.work.ip.address/<my ip address>/g" | \
sed -ue "s/hostname/server/g"
Run and copy/paste.
not bad, although i’m not sure how distro-agnostic this is. also, no postgres version. 
e: we’re hijacking the thread tho
Hi,
I’m getting the same error:
E_ERROR (1) classes/feeditem/rss.php:199 Cannot use object of type DOMNodeList as array
I have read and tride a number of things suggested here, there is no change.
I have created a HTACCESS file, forcing TT-RSS to use PHP 7
AddHandler application/x-httpd-php70 .php
as suggest by my hosting service
And as some have suggested, this hapenned after I did an update regarding the AF_language plugin
I’m on a shared server and have had NO problems until this weekend
TT-RSS - Current
PHP - 7.0.7
MySQL -
Server: Localhost via UNIX socket
Server type: Percona Server
Server version: 5.5.50-38.0-log - Percona Server (GPL), Release 38.0, Revision b05b24c
Protocol version: 10
Thats it!
Thanks for the help
Stacey
you need to contact your hosting support because that htaccess thing you did isn’t working
ask them to help you switch to php 7
I got past the previous errors I was having and now am seeing a new error. The previous error led use php 5.6 and now this new error led me to enable modules in php.ini. I can log in again now but I am still getting the error when I manually try an update. (My cron job for updating was failing so I tried a manual update.)
- PHP support for PostgreSQL is required for configured DB_TYPE in config.php
Could something be calling the older version of php still?
php has different ini files for its various binaries - i.e. a command line binary used by update.php might not have same modules enabled, normally distro deals with this stuff for you automatically but it wouldn’t hurt to check.
alternatively, your php command line binary points to wrong php version, although in that case you’d get version check error.
I knew this day would come. I know I’m on a no longer supported LTS of Ubuntu. I don’t blame the developers. They are great.
Like everyone else here, yesterday my feed updates broke and today I got an update to php5.6 message. Updating to 5.6 on my current LTS does not look possible. My solution in the near term is to roll back a few commits till updates start working and stay at that commit in the near term. I did this via the following command.
- Kill all update agents that are running
- sudo git checkout 32c0c07cc1fb1019a61b83814bdd7c3830b621e6
This is the approximate location just before things stopped working. - Start update agents.
Worked for me, until I invest the time in a new Ubuntu LTS install. Sucks because I have several systems and they are intertwined. I’ll be down for at least a weekend… probably longer.
Does anyone have a how-to for migrating ttrss dbs?
Thanks,
Jon
just how ancient your LTS install is that there’s not even php 5.6 backport for it?
also: imagine all the long fixed vulnerabilities it still has
you pretty much just dump and restore it with tools provided by your database.
Hi Fox,
Thank you, I was able to figure out what I had not done.
My .htaccess file was correct, but because of the way my sever is setup I needed to specify the complete path to the version of PHP I’m using. My cron jobs needed the same full path.
Everything seems to have updated withoout any errors.
Thanks again for TT-RSS and your help
Stacey
I’m on 12LTS. Dist upgrades NEVER go well. I learn along time ago to do a clean/fresh install all at once they nurse ver along till something fundamentally breaks or a new feature, I want, is simply not back-portable. Then I’ll just do a clean install on all my machines, with a fresh drives, and migrate config over.
I really don’t have that much exposure. Everything is either https or ssh with very few ports open to the WAN. Besides that, I’m supremely uninteresting and try to stay that way. If someone really wants my NPR feed… they can have it. 
i don’t know about ubuntu but i’ve been dist-upgrading several debian machines since 2003.