Opened 8 months ago
Last modified 8 months ago
#68009 new enhancement
Improvement to logging for installation of Mariadb server
| Reported by: | jasimon9 | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | michaelld (Michael Dickens) | |
| Port: | mariadb-10.6 |
Description
I had problem upgrading mariadb-10.6-server that took very long to solve. It would have been made much easier if the logging that gave the solution was also included at the end of the log output along with the other notes pertaining to various ports. So this ticket is just a request to improve the macports logging for the mariadb server ports.
The situation appears to be something like the following (because I don't have the full log it has to come from memory):
- task is to upgrade mariadb-10.6-server
- during the process, macports has to uninstall mariadb-10.6 apparently after the mariadb-10.6-server is done
- but because mariadb-10.6 is dependent upon the server, a notice is displayed about that, but then it goes ahead to force the uninstall and upgrade of mariadb-10.6. The key part is that there is a notice stating to the effect that the server mariadb-10.6-server has to be reinstalled.
- I did not originally see that. The result was apparently that the server install is corrupted such that is has to be redone.
- The result is that the commands to unload and reload the server shown below appeared to function properly, but mariadb as mysqld was not running.
- sudo port unload mariadb-10.6-server
- sudo port load mariadb-10.6-server
I could not do any of the usual things to get it to run. Further, there was nothing in the error log.
I finally got it fixed by realizing that the install of the server had to be executed by itself, and then the unload/reload sequence. After that all was again good.
A lot of grief could have been avoided simply by taking that error message that was obscured by being hidden in all the output and putting at the end in a "mariadb-10.6-server has the following notes" section.
Change History (4)
comment:1 Changed 8 months ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | michaelld added |
|---|
comment:2 Changed 8 months ago by jmroot (Joshua Root)
| Milestone: | MacPorts Future |
|---|---|
| Port: | mariadb-10.6 added |
comment:3 Changed 8 months ago by ryandesign (Ryan Carsten Schmidt)
comment:4 Changed 8 months ago by jasimon9
Unfortunately it is hard to understand what I am trying to explain, but if I did have the original full log, it would be apparent exactly what is going on. It would be easy to see the critical message that is part of the log and which should also be added to the notes at the end.
This is a mission critical system in daily production and I don't really want to experiment with it. I do have a duplicate backup computer that I would be willing to experiment with. The most ideal and organic way would be to have outdated ports on that machine and be in need of a port upgrade. But the ports are all up to date now on that machine too.
How could I try to do such an upgrade at this point?
I'm not sure what you're talking about:
Replying to jasimon9:
That doesn't make sense. mariadb-10.6-server depends on mariadb-10.6. mariadb-10.6-server requires mariadb-10.6 to be installed. MacPorts won't uninstall it.
Perhaps you mean that the rev-upgrade process, which runs after every install or upgrade, analyzed your installed ports and found mariadb-10.6 to be broken?
Normally rev-upgrade rebuilds the port for you to work around the breakage. If rebuilding fixed the breakage, then the bug may be that someone forgot to increase the revision of the port after one of its dependencies was updated. Debug output from the rev-upgrade process, run when the port was broken, would let us know if that was the case.
If rebuilding doesn't fix the breakage, rev-upgrade reports that to you. In that case, installing it manually shouldn't do anything different and shouldn't fix it either.
So it's very unclear what happened in your situation or what fixed it. We can't add any notes to the port or to MacPorts in general to describe something we don't understand, and it sounds like an undesirable situation that should be fixed rather than adding a note about it. But we would need to see the log you don't have to understand what happened and what to do about it.