[batdroid]

I have recently migrated my data to a new Synologyy (DS1621+) from DS412. Kodi had been working for over 8 years with no issues

Once the migration was complete, I have had numerous issues with getting my Synology to connect to Kodi, and I think I have narrowed down the latest issue but need some help

After the migration was complete, both MariaDB and phpMyAdmin had to be repaired via my package centre

I then had to create a new password for php via MariaDB

ISSUES
I am trying to create a new user, but privileges (tab) does not appear in the top list of tabs. It’s my understanding this tab should be visible

If I try to create a new user (u/n: xbmc & p/w: xbmc) within user accounts,  I get the following error:
#1819 - Your password does not satisfy the current policy requirements: [Minimal password length 10, Include mixed case, Include numeric characters, Include special characters, Exclude name of user from password]

I am at a loss on how I should proceed here.

Is it customary for this process to break during the migration process?

Log File: https://paste.kodi.tv/ameqofuveq

[dpar]

I have recently migrated my data to a new Synologyy (DS1621+) from DS412. Kodi had been working for over 8 years with no issues

Once the migration was complete, I have had numerous issues with getting my Synology to connect to Kodi, and I think I have narrowed down the latest issue but need some help

After the migration was complete, both MariaDB and phpMyAdmin had to be repaired via my package centre

I then had to create a new password for php via MariaDB

ISSUES
I am trying to create a new user, but privileges (tab) does not appear in the top list of tabs. It’s my understanding this tab should be visible

If I try to create a new user (u/n: xbmc & p/w: xbmc) within user accounts,  I get the following error:
#1819 - Your password does not satisfy the current policy requirements: [Minimal password length 10, Include mixed case, Include numeric characters, Include special characters, Exclude name of user from password]

I am at a loss on how I should proceed here.

Is it customary for this process to break during the migration process?

Log File: https://paste.kodi.tv/ameqofuveq

The answer is above - It's telling you that you don't meet the password requirements. One of the requirements is that you can't include the username in the password, which is what you're doing if you're trying to create a username of xbmc and a password of xbmc. I would just create a password that meets the requirements and update it in Kodi?

I seem to remember there used to be a way to disable those password requirements, but it's really easy to change it in Kodi if you're using a sources.xml.

[Klojum]

The answer is above

Please keep in mind when and when not to quote an entire forum post to get someone's attention. Quoting an entire post right after that post is like two old people chatting while having hearing problems and repeating each others' remarks. That's often not really necessary on a forum.

Kodi's forum has a neat feature where you can select a section that you actually want to respond to. Select a text portion with your mouse (or finger on a touch screen), and a "Reply" bar will appear under that post. Click it and the selected text will be inserted as a quote. Quite simple and more precise than lazily hitting the quote button. Otherwise, just use the @Name option.

@batdroid
It seems that Synology has reconstructed its latest DSM firmware quite a bit. I myself still have to digress all the changes in DSM 7 affecting Kodi (with 7.1 coming up), so perhaps we can list all applicable changes to Kodi and have them in the Kodi Wiki where necessary. The 10-char length password is something I didn't know of, but sometimes password requirements can be changed by the administrator of the NAS/network. But as said, most of the new stuff is still uncharted territory for me.

[batdroid]

 

Thanks, that was the issue but wish it had notified me while I was still on the old nas box

[batdroid]

@batdroid
It seems that Synology has reconstructed its latest DSM firmware quite a bit. I myself still have to digress all the changes in DSM 7 affecting Kodi (with 7.1 coming up), so perhaps we can list all applicable changes to Kodi and have them in the Kodi Wiki where necessary. The 10-char length password is something I didn't know of, but sometimes password requirements can be changed by the administrator of the NAS/network. But as said, most of the new stuff is still uncharted territory for me.

Yep.  very interesting indeed. However, with the migration and password change, the database has lost all my watched data :-(

I am still looking into how I can get it back but no luck. This is beyond frustrating

[Klojum]

I am still looking into how I can get it back but no luck.

A Kodi database migration should not "lose" the watched data. It is stored in the "files" database table. Also, making SQL dumps (=backups) is a good thing to do from time to time. With the right tool, it takes merely seconds.

if you still have the old database, you could do a Video Library Export from that one to create nfo files. You will need to first 'activate' the watched state and resume points in the advancedsettings.xml file.

[batdroid]

 

thanks for getting back to me.

I looked on the old database but it was nowhere to be found :-(

After the migration, I was forced to update Maria and myphp on the old nas. Once I logged onto to PHP, it was empty. My previous user "xbmc" was no longer listed.

it's possible I did something wrong but had to tell.

What tool do you recommend for backing up?

[Klojum]

I looked on the old database but it was nowhere to be found :-(

An older database is not removed by Kodi during a Kodi update.
Now it's a case of the MySQL/MariaDB server (and PHP) that was updated via DSM7. This should not affect the contents Kodi database itself. If the Kodi database password would be changed, that would surprise me quite a bit.

My previous user "xbmc" was no longer listed.

Again, a database server update should not affect the current database contents. Database users should not be removed.
But there is the odd possibility that you yourself removed one thing or the other.
A kodi database user ('xmbc' or something else) can be recreated. You should also see if you can get access via "root" to the database, if that works, then you have God-mode as the database admin.

What tool do you recommend for backing up?

There are basically two types: a web-interface version and a dedicated tool.

On your NAS you can probably install PhPMyAdmin as a web-application.
With stand-alone tools, I typically use MySQL Workbench.
Both tools have the ability to backup and restore databases.

[batdroid]

 

i hear you and it's probably but I am not the most technical person out there.

My root access no longer worked after the update and I was forced to create a new one. But as you stated, it might have been my error. However, I have no way to tell :-(

[DarrenHill]

Can you confirm which version of Mariadb/MySQL you were running under DSM6, compared to what you are running now under DSM7?

You note that you had to update the version when you went from DSM6 to DSM7, and I wonder if by doing that the system essentially uninstalled the old version and installed the new one, and the database got lost in the process.

On my Synology (a 1016+) I've also done the update from DSM6 to DSM7, but I was on the latest MariaDB version for both, and I don't think it touched it at all. Certainly I didn't lose the database nor any access etc in the migration update. For me it was seamless, but perhaps I was "lucky" in that I saw in the changelogs for DSM what would be happening (earlier MariaDB versions being depreciated and removed) and ensured that things were fully up to date before doing the DSM update.

[batdroid]

Can you confirm which version of Mariadb/MySQL you were running under DSM6, compared to what you are running now under DSM7?

You note that you had to update the version when you went from DSM6 to DSM7, and I wonder if by doing that the system essentially uninstalled the old version and installed the new one, and the database got lost in the process.

On my Synology (a 1016+) I've also done the update from DSM6 to DSM7, but I was on the latest MariaDB version for both, and I don't think it touched it at all. Certainly I didn't lose the database nor any access etc in the migration update. For me it was seamless, but perhaps I was "lucky" in that I saw in the changelogs for DSM what would be happening (earlier MariaDB versions being depreciated and removed) and ensured that things were fully up to date before doing the DSM update.

Unfortunately, i can't tell. My plan had been to utilise the old Nas to backup the database entries but after the migration, both maria and SQL were unusable unless I upgraded.

I think you are spot on with your assessment about the old version being uninstalled. it's the only logical conclusion.

Lesson learned re updating all key software. However, I do wish I had been promoted to carry it out.

[DarrenHill]

Personally I'd also echo what was recommended above, to periodically export your database as individual files to anyone who is running a NAS set-up like yours (and mine). That will write NFO (wiki) files for each of your movies and show episodes beside the actual media files, storing all the information safely there.

That way if your database gets corrupted (or you just want to add a new device that isn't on the central MySQL (wiki) database), all you need to do is a simple rescrape and it will build it again. And it should be relatively quick, as all the information is local (especially if you've used Artwork Dump or similar to also store posters etc locally) and so no internet access or downloading is required to recreate everything.

[scott967]

Think I will stick to DSM 6.2 for a while!  I only use MariaDb for testing, but still don't need the hassle (for some reason I'm on port 3307 and don't have any problems).  But I worry about something going wrong with my RAID going 6.2>>7.

Release notes for DSM 7 does say MariaDb 5 not supported, you need to be on 10.  Agree it's probably best to update your packages (and confirm all is working) prior to doing the 6.2>>7.

On windows I am using Heidisql to verify connection to MariaDb.

scott s.
.

[Klojum]

I have (limited) access to an already upgraded DSM7 Syno NAS, but the whole DSM upgrade process all sounds very fucky to me. I still use MySQL 5.7 separately on a Ubuntu "NAS" machine, and I think I'll stick to that as long as possible. I'll try to do some testing on the DSM7 NAS just for laughs, but Synology and MariaDB seem to create their own quirks just for the heck of it.

[batdroid]

 

Yep, lesson learned the hard way.