Tuning Primer - No Valid Socket File - sockets

I am trying to run Tuning Primer using Cygwin on my Windows 7 computer to check some of my databases.
Whenever I try to run it, It gives me the following error:
No valid socket file "" found!
/cygdrive/c/Users/MID-PC/Downloads/tuning-primer.sh: line 109: tput: comando não encontrado
The mysqld process is not running or it is installed in a custom location.
/cygdrive/c/Users/MID-PC/Downloads/tuning-primer.sh: line 109: tput: comando não encontrado
If you are sure mysqld is running, execute script in "prompt" mode or set
/cygdrive/c/Users/MID-PC/Downloads/tuning-primer.sh: line 109: tput: comando não encontrado
the socket= variable at the top of this script
/cygdrive/c/Users/MID-PC/Downloads/tuning-primer.sh: line 109: tput: comando não encontrado
Any Idea of how can I manually set this socket?
(Yes, I do have MySQL running on this machine)

Related

How can fixed this error in moodle update?

HelloW!
When I went to upgrade moodle 3.10 to 3.11 and later 4.x.
I got a problem, after installing all the plugins that weren't on disk, and others that weren't found.
When proceeding, I had this image error.
Error Image Print
I use moodle in PT-BR, this is an error log:
Atualizando para nova versão
Importação de idioma: pt_br_old
Impossível achar componente
Outras informações sobre este erro
Informações de depuração: pt_br_old
Error code: cannotfindcomponent×Ignorar essa notificação
Rastreamento de pilha:
line 810 of /lib/componentlib.class.php: lang_installer_exception thrown
line 665 of /lib/componentlib.class.php: call to lang_installer->install_language_pack()
line 45 of /admin/tool/langimport/lib.php: call to lang_installer->run()
line 1741 of /lib/upgradelib.php: call to tool_langimport_preupgrade_update()
line 1856 of /lib/upgradelib.php: call to upgrade_language_pack()
line 519 of /admin/index.php: call to upgrade_core()
log in english:
Updating to new version
Language import: pt_br_old
Impossible to find component
Other information about this error
Debug info: pt_br_old
Error code: cannotfindcomponent×Ignore this notification
Stack tracking:
line 810 of /lib/componentlib.class.php: lang_installer_exception thrown
line 665 of /lib/componentlib.class.php: call to lang_installer->install_language_pack()
line 45 of /admin/tool/langimport/lib.php: call to lang_installer->run()
line 1741 of /lib/upgradelib.php: call to tool_langimport_preupgrade_update()
line 1856 of /lib/upgradelib.php: call to upgrade_language_pack()
line 519 of /admin/index.php: call to upgrade_core()
I installed all the missing plugins on the disk given in the update.
I downloaded and installed the PT-BR Moodle 3.11 language pack in the lang folder and also cleared the cache of the folders inside moodledata in my case it has another name. But i don't delete lang folder in moodledata and exist content in this folder.
path moodledata: /var/AnotherName
I updated the system, ubuntu, entered the permissions in the folder again and nothing worked until now.
I kept the config.php from the old moodle as recommended. The only warning I got in the update was about input_vars below 5000, and about the database not being in exact moodle format. But it was just warnings.

postgres installation error post-bootstrap FATAL: invalid byte sequence

I'm trying to install Postgres 13 (Windows version), but I always obtain same error (part is in Spanish):
realizando inicializaci¢n post-bootstrap ... 2021-04-30 12:10:54.935 CEST [1224] FATAL: invalid byte sequence for encoding "UTF8": 0xbf
el proceso hijo termin¢ con c¢digo de salida 1
initdb: eliminando el contenido del directorio ®C:/PostgreSQL13/data¯
Called Die(Failed to initialise the database cluster with initdb)...
Failed to initialise the database cluster with initdb
Script stderr:
Program ended with an error exit code
Error al ejecutar C:\WINDOWS\System32\cscript //NoLogo "C:\PostgreSQL13/installer/server/initcluster.vbs" "NT AUTHORITY\NetworkService" "postgres" "****" "C:\Users\user1\AppData\Local\Temp/postgresql_installer_b86f3c1062" "C:\PostgreSQL13" "C:\PostgreSQL13\data" 5432 "English,UnitedStates" 0 : Program ended with an error exit code
Problema al ejecutar el paso post instalación. La instalación no pudo finalizar correctamente
La inicialización del clúster de la base de datos falló.
User user1 has administrator rights. I have also tried to install version 12 instead of 13, but the result is the same.
Any suggestions?
This is very likely because the database superuser name contains non-ASCII characters.
I don't know exactly how you install PostgreSQL, but this probably happens when you run initdb to create a data directory (which would fit with the "initcluster" script in your message).
If you don't specify a superuser name by using the -U option of initdb (it is customary to use the nae postgres), initdb will name the superuser like your current operating system user. If you are on Windows, that name will be encoded in a Windows encoding like Windows-1252. Now the database doesn't know that, and when it creates the database user, it uses the very bytes of that user name. If that is not correctly encoded UTF-8 (which is won't be if it contains non-ASCII characters), that causes this error.
My suggestion is that you log on to Windows with an operating system user that has all ASCII characters in its name and try again.

Error when using a newly installed module with Perl 5.26

I have just installed Strawberry Perl 5.26 on a Win32 machine (XP), and installed Device::ParallelPort (with cpanm, and the installation is OK).
When I try to use the module, I have :
Device::ParallelPort unabel to create driver auto (see Device::ParallelPort::drv::auto for further information) - Device::ParallelPort::
drv::auto (auto detect) error
failed to load win32 - Can't locate Device/ParallelPort/drv/win32.pm in #INC (you may need to install the Device::ParallelPort::drv::win
32 module) (#INC contains: Q:/APPS/Perl-5.26/perl/site/lib/MSWin32-x86-multi-thread-64int Q:/APPS/Perl-5.26/perl/site/lib Q:/APPS/Perl-5
.26/perl/vendor/lib Q:/APPS/Perl-5.26/perl/lib) at (eval 3) line 2.
BEGIN failed--compilation aborted at (eval 3) line 2.
. Make sure you have loaded and installed Device::ParallelPort::drv::win32 from CPAN. Install Device::ParallelPort::drv::(linux|parport|
win32) and try again at (eval 2) line 3.
at Q:\VirtualDiskII\Perl\testlpt.pl line 25.
So I have installed Device::ParallelPort::drv::win32 (and the installation is OK). When trying to use the module, I have :
Device::ParallelPort unabel to create driver auto (see Device::ParallelPort::drv::auto for further information) - Device::ParallelPort::
drv::auto (auto detect) error
failed to load win32 - Failed to load inpout32.dll - Can't create Inp32 2 - Une requÛte d'envoi ou de rÚception de donnÚes n'a pas ÚtÚ a
utorisÚe car le socket n'est pas connectÚ et (lors de l'envoi sur un socket datagramme en utilisant un appel sendto) aucune adresse n'a
ÚtÚ fournie. at Q:/APPS/Perl-5.26/perl/site/lib/Device/ParallelPort/drv/win32.pm line 75.
. Make sure you have loaded and installed Device::ParallelPort::drv::win32 from CPAN. Install Device::ParallelPort::drv::(linux|parport|
win32) and try again at (eval 2) line 3.
at Q:\VirtualDiskII\Perl\testlpt.pl line 25.
Any ideas ?
Thank you by advance !
According to the Device::ParallelPort::drv::win32 docs...
Standard installation, but you also need "inpout32.dll" which may require either putting into your windows System directory, or at the location of your executable.
inpout32.dll actually comes from a 3rd party source and is freely available.
http://www.logix4u.net/inpout32.htm
Unfortunately that site appears to no longer work. You'll have to find another source.
If you wanted to get ambitious, you could patch the module to handle this automatically and, if the DLL's license allows, ship with the DLL. Or write an Alien wrapper module.

Not found for CancelIoEx in Windows xp

Socket TCP, in C++ with QT, compiled in MinGW 32 bits for pc windows XP service pack 1.
Error : not found for CancelIoEx "No se encuentra el punto de
entrada del procedimiento CancelIoEx en la biblioteca de vinculos
dinamicos kernel.32.dll"
The CancelIoEx function wasn't added until Windows Vista:
Requirements
Minimum supported client: Windows Vista [desktop apps | UWP apps]
That is why you cannot find it in Windows XP.

Perl debugger error # C:/Perl/lib/Term/ReadLine/Perl.pm line 65

I'm having a strange error trying to run a Perl script with ActivePerl on Windows XP:
>perl -d quick_translate_missing.pl < translate_en.txt > new.txt
Loading DB routines from perl5db.pl version 1.33
Editor support available.
Enter h or `h h' for help, or `perldoc perldebug' for more help.
main::(quick_translate_missing.pl:9):
9: my $not_translated = '\'EN_([\w\s]+)\'';
El sistema no puede hallar la ruta especificada.
Unknown error
Compilation failed in require at C:/Perl/lib/Term/ReadLine/Perl.pm line 65.
at C:/Perl/lib/Term/ReadLine/Perl.pm line 65
Term::ReadLine::Perl::new('Term::ReadLine', 'perldb', 'GLOB(0x1968f34)',
'GLOB(0x1927e7c)') called at C:/Perl/lib/perl5db.pl line 6068
DB::setterm called at C:/Perl/lib/perl5db.pl line 2241
DB::DB called at quick_translate_missing.pl line 9
Attempt to reload Term/ReadLine/readline.pm aborted.
Compilation failed in require at C:/Perl/lib/Term/ReadLine/Perl.pm line 65.
END failed--call queue aborted at quick_translate_missing.pl line 65.
at quick_translate_missing.pl line 65
"El sistema no puede hallar la ruta especificada." means "System cannot find the specified path". The line the error is referring to is from Perl.pm:
eval {require Term::ReadLine::readline}; die $# if $#;
What I understand is that it cannot find Term::ReadLine::readline, but the file C:\Perl\lib\Term\ReadLine\readline.pm is there. Also PATH is set correctly since I can run perl interpreter from anywhere without specifing the path.
The error happens only when using standard output redirection (>). Script passed to debugger doesn't matter, it crashes on all if output redirection used.
Any clues? Thanks in advance!
This may not help you if you must have a specific perl version, but I found this same error with my perl 5.8.5 install. I could not upgrade on one machine (for legacy code reasons), but I ran it in another perl environment with the latest perl (v5.14.2) and this "debugger" bug has been solved (although I suspect you may have the same result by updating the Term::ReadLine::* modules as well). By the way, this isn't specific to ActivePerl -- I saw this on Linux as well.