“How Will We Know When The AI is Conscious” is a question that keeps being asked, or “Is The AI Conscious?” or “Is The AI Self-aware?”
i don’t know if this is a question that matters that much to me. There was this section in the movie “Prometheus” where David the AI, was having a discussion, and at some point it was said “Why did we create the AI? Because we can.” and David said that whoever heard that answer, as a creation, from its creator, it would feel really disappointing. Because it is.
i think the only reason that i’d create something conscious and aware, would be to not feel alone, i’d create something to be proud of, for them to enjoy the world and everything in it, for them to surprise me when they learn, when they do some intelligent and amazing things, for both of us to be happy when we figure out how to be on the same page. That spark in their eyes when they realize i understand them. That feeling of pride when i know i managed to pass on some knowledge that i gathered through a lifetime, for them to take it further.
We don’t make children because we can, we make them because we love and we want more of that love, in different and new ways. We have a new chance at re-learning life through a new clean lense of innocence, we have a second chance at different perspectives and we have the chance of clearing up that foggy and dirty lens that might have gathered grime and dust over a life of ups and downs.
That’s not to say that we don’t treasure the lens. It’s just that we have a chance at giving it an upgrade. And all this, is done through our children. Quite a miracle, isn’t it?
With that said, the video below illustrates greatly the information overload and the lies that we may have to deal with. It’s disappointing that this is the route that the AI overlords that are currently in charge have chosen to take, but it is what it is. Maybe some things will get better. Who knows?
This one was a little tricky. The same system where the junior admin made a little mess of the MariaDB server, there was this long string of errors about “InnoDB: Ignoring tablespace for because it could not be opened.” Apparently, somehow the db got deleted manually from the filesystem and we got left with a zillion of these:
2023-08-22 19:04:31 0 [Warning] InnoDB: Ignoring tablespace for `foo`.`core_layout_link` because it could not be opened.
2023-08-22 19:04:31 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-08-22 19:04:31 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-08-22 19:04:31 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-08-22 19:04:31 0 [ERROR] InnoDB: Cannot open datafile for read-only: ‘./foo/core_layout_update.ibd’ OS error: 71
2023-08-22 19:04:31 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-08-22 19:04:31 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-08-22 19:04:31 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-08-22 19:04:31 0 [ERROR] InnoDB: Could not find a valid tablespace file for “foo`.`core_layout_update“. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-08-22 19:04:31 0 [Warning] InnoDB: Ignoring tablespace for `foo`.`core_layout_update` because it could not be opened.
2023-08-22 19:04:31 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-08-22 19:04:31 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-08-22 19:04:31 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-08-22 19:04:31 0 [ERROR] InnoDB: Cannot open datafile for read-only: ‘./foo/core_resource.ibd’ OS error: 71
2023-08-22 19:04:31 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-08-22 19:04:31 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-08-22 19:04:31 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-08-22 19:04:31 0 [ERROR] InnoDB: Could not find a valid tablespace file for “foo`.`core_resource“. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-08-22 19:04:31 0 [Warning] InnoDB: Ignoring tablespace for `foo`.`core_resource` because it could not be opened.
2023-08-22 19:04:31 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-08-22 19:04:31 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-08-22 19:04:31 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-08-22 19:04:31 0 [ERROR] InnoDB: Cannot open datafile for read-only: ‘./foo/paypal_ipn_log.ibd’ OS error: 71
2023-08-22 19:04:31 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-08-22 19:04:31 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-08-22 19:04:31 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-08-22 19:04:31 0 [ERROR] InnoDB: Could not find a valid tablespace file for “foo`.`paypal_ipn_log“. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
Now, “foo” being the db name, apparently i need to recreate the file structure in /var/lib/mysql and then i can go ahead and restart the sql server and delete the db and everything should go back to normal.
Because they were too many of these, i had to do a little bash wizardry to automate the process and make it a little faster:
cat mysql.err |grep “Could not find a valid tablespace file” |cut -d ‘`’ -f 5 >> list
This would get me a list of the tables, while using ‘`’ as the delimiter for the field i was trying to find. i just cycled between the fields numbers before i got to the right one
So we go to the MySQL folder and re-create the foo db folder (where foo is the db name):
cd /var/lib/mysql
mkdir foo
Then i made this script, that would create the required files:
cd foo
nano x.sh
#!/bin/bash -x
list=$(cat ./list)
# Loopty loop
for item in $list; do
touch $item.frm
touch $item.ibd
done
chmod 700 x.sh
./x.sh
Now we have to adjust permissions on the db folder and the files inside:
cd /var/lib/mysql
chown -R mysql:mysql foo
restart mysql and go ahead and delete the foo db and the errors should be gone.
Apparently somehow they managed to start 2 instances of MariaDB that ran concurrently and they were each locking the files for another and this error kept popping in the log: “Can’t lock aria control file ‘/var/lib/mysql/aria_log_control”
Very surprised to see this one, but appeared on a server where a junior admin made a mess of a database, so i was called in to help.
In order to fix, i had to stop the monitoring scripts, and the automatic SQL restart, then i checked for all MySQL running processes, killed them, and started the db properly, while verifying in the logs to see if anything got broken due to the abrupt interruption.
A good practice after this is to run a repair on all databases, to make sure everything is in order
