Hi, (CCing Thomas).
El 25/10/24 a las 13:25, Santiago Ruano Rincón escribió: > Control: tag -1 + moreinfo > > El 04/02/24 a las 10:24, Picca Frédéric-Emmanuel escribió: > > Package: tango-db > > Severity: important > > X-Debbugs-Cc: [email protected] > > > > Dear Maintainer, > > > > I upgraded a computer from bullseye to bookwork. tango-db was > > installed with the bulleyes version before the upgrade. > > > > The upgrade went fine, so I installed the tango-starter (bookworm > > version). > > > > BUT the tango-starter could not register in the database. > > > > So I wipeout all of tango-xxx, remove the sql database. > > > > then I re-installed the tango-db and tango-starter. This time the > > starter worked out of the box. > > > > In fact I was affected by this > > > > https://gitlab.com/tango-controls/TangoDatabase/-/issues/69 > > > > the fresh install script of the sql databse and the upgrade scripts > > used by dbconfig-common, does not produce the same sql database at the > > end. > > > > the new create_db_tables was modified like this > > > > https://gitlab.com/tango-controls/TangoDatabase/-/merge_requests/82/diffs > > > > So during the upgrade the tables should be alter to take into account > > this modification. > > > > https://gitlab.com/tango-controls/TangoDatabase/-/issues/26 > > > > the bug is triggered only because mariadb changed it's behaviour > > between bullseye and bookworm. > > > > It would be great to fix bookworm. > > > > thanks > > > > Frederic > > Hi Frédéric, > > I am unable to reproduce the issue. I have followed these steps: > > 1. Create a bullseye container, apt install mariadb-server tango-db > 2. Upgrade to bookworm > 3. apt install tango-starter > > Maybe I am missing something, but AFAICS, tango starter was registered > in the database: > > tango_admin --ping-device dserver/Starter/bullseye-tango-db ; echo $? > 0 > > The current mariadb-server installed is 1:10.11.6-0+deb12u1. > > Do you have more information that could help to reproduce the issue? Wouldn't you reporting an issue about a bookworm -> trixie upgrade? I have tried the above mentioned steps upgrading from bookworm to testing, and tango-starter is unable to start: Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Tango exception Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Severity = ERROR Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Error reason = DB_SQLError Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Desc : Failed to query TANGO database (error=Field 'date' doesn't have a default value) Oct 25 14:40:32 bookworm-tango-db Starter[11770]: .The query was: INSERT INTO property_device_hist SET device='tango/admin/bookworm-tango-db',id='43',name='polled_attr',count='1',value='hoststate' Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Origin : DataBase::db_put_device_property Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Tango exception Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Severity = ERROR Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Error reason = API_CommandFailed Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Desc : Failed to execute command_inout on device sys/database/2, command DbPutDeviceProperty Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Origin : virtual CORBA::Any_var Tango::Connection::command_inout(const std::string&, const CORBA::Any&) at (./lib/cpp/src/client/devapi_base.cpp:1531) Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Received a CORBA_Exception Oct 25 14:40:32 bookworm-tango-db Starter[11770]: Exiting Oct 25 14:40:32 bookworm-tango-db systemd[1]: tango-starter.service: Deactivated successfully. Frédéric, would you mind confirming this? Cheers, -- Santiago
signature.asc
Description: PGP signature
-- debian-science-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
