I'm trying to execute a sql script using snowsql in below ways:
option1: !source C:\Users\"Local PC"\Documents\snowsql\test.sql;
or
!source C:\Users\Local%20PC\Documents\snowsql\test.sql;
I'm getting the below error. File is available in the location specified. Am I missing anything here?
[Errno 22] Invalid argument: C:\Users\Local%20PC\Documents\snowsql\test.sql.
Please let me know if I'm wrong anywhere
I resolved the issue: I copied the file into the Current working directory on my windows machine(In my case, it was just \Users\Local%20PC) and then ran the command as below
!source test.sql
Related
This is the first time i'm using openstack, I'm really a new one, I'm doing right now an OpenStack packstack installation, I've generated an answer file in which i specify the following parameters : (notice that I've followed a website doing that i don't know exactly what does all of these parameters means)
CONFIG_PROVISION_DEMO=n
CONFIG_NEUTRON_ML2_TYPE_DRIVERS=flat,vxlan
CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=vxlan
CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS=openvswitch
CONFIG_NEUTRON_L2_AGENT=openvswitch
CONFIG_NEUTRON_OVS_EXTERNAL_PHYSNET=extnet
CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=extnet:br-ex
CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-ex:em1
I'm getting the following error :
ERROR : Error appeared during Puppet run: 10.53.193.172_controller.pp Notice: /Stage[main]/Nova::Db::Sync/Exec[nova-db-sync]/returns: Error: (pymysql.err.OperationalError) (1045, u"Access denied for user 'nova'#'10.53.193.172' (using password: YES)") (Background on this error at: sqlalche.me/e/e3q8) You will find full trace in log /var/tmp/packstack/20210401-074033-eKhyZ8/manifests/10.53.193.172_controller.pp.log
I've search how to solve it,and i didn't find anything helpful, so i ignored it and I've try to re-run the packstack --answer-file=answerfile.txt, and I'm getting this time a new error :
ERROR : Error appeared during Puppet run: 10.53.193.172_controller.pp
Error: Failed to apply catalog: Could not authenticate
You will find full trace in log /var/tmp/packstack/20210401-082518-KWFGCT/manifests/10.53.193.172_controller.pp.log
Please check log file /var/tmp/packstack/20210401-082518-KWFGCT/openstack-setup.log for more information
Any help, please !
I'm getting an error while attaching a file to the mail post Jenkins job.
ERROR: Error accessing files to attach: Expecting Ant GLOB pattern, but saw '/Test/reports/test_report.html' See http://ant.apache.org/manual/Types/fileset.html for syntax
Just a workaround, copy the file from its location to $WORKSPACE
cp $WORKSPACE/Test/reports/test_report.html $WORKSPACE/test_report.html
and just specify "test_report.html" in attachment field of your jenkins.
My knowledge is at a very basic level.
But I have special task for running Apache.
FreeBSD 8.1
At first, when I tried to perform command:
#apachectl start
was an error:
[warn](2) No such file or directory: Failed to enable the 'httpready' AcceptFilter
[warn](2) No such file or directory: Failed to enable the 'dataready' AcceptFilter
Then I added to the file /boot/loader.conf :
accf_http_load="YES"
accf_data_load="YES"
And when I perform
#/usr/local/etc/rc.d/apache22 start
I get this:
Performing sanity check on apache22 configuration:
Syntax OK
Starting apache22.
/usr/local/etc/rc.d/apache22: WARNING: failed to start apache22
Command:
#apachectl start
returns without any errors
In httpd-error.log I can see only this:
(21)Is a directory: httpd: could not open error log file /home/httpd-logs/hostname.example.error.log.
Unable to open logs
So the question is: How to start apache22 ?
Problem solved!
The reason was in bad extension of error log files that was written in httpd.conf for VirtualHost
That's why I saw message
(21)Is a directory: httpd: could not open error log file /home/httpd-logs/hostname.example.error.log.
Unable to open logs
in /var/log/httpd-error.log
So i just create new log files in /home/httpd-logs/ where they were all recorded
Assumming the following error is because the same path on local system does not exist on the remote system.
Is there a way to specify an alternative path to save on remote system?
[root#linuxsystem mydir]# staf local FS COPY FILE /root/scripts/tests/script.bat TOMACHINE remoteVM
Error submitting request, RC: 17
Additional info
---------------
\root\scripts\tests\script.bat
Error information:
17 File Open Error
This indicates that there was an error opening the requested file.
Some possible explanations are that the file/path does not exist, contains invalid characters, or is locked.
Note: Additional information regarding which file could not be opened may be provided in the result passed back from the submit call.
Found correct command:
staf local FS COPY FILE /root/scripts/tests/script.bat TODIRECTORY "C:\" TOMACHINE remoteVM
im trying to setup a small 2 system distcc compile cluster for a new project im working on but for some reason i cant get the second server in the cluster to compile.
the arm-eabi-gcc file works if i try to run it on said server i get the normal no input files error but distcc has other ideas.
extract from its log file :
distccd[13005] (dcc_execvp) ERROR: failed to exec arm-eabi-gcc: No such file or directory
distccd[13002] (dcc_job_summary) client: xxx.xxx.xxx.xxx:32890 COMPILE_ERROR exit:110 sig:0 core:0 ret:0 time:1103ms arm-eabi-gcc arch/arm/vfp/vfpdouble.c
distccd[13003] (dcc_pump_readwrite) ERROR: unexpected eof on fd5
distccd[13003] (dcc_job_summary) client: xxx.xxx.xxx.xxx:32891 CLI_DISCONN exit:0 sig:0 core:0 ret:107 time:429ms
distccd[12998] (dcc_pump_readwrite) ERROR: unexpected eof on fd5
distccd[12998] (dcc_job_summary) client: xxx.xxx.xxx.xxx:32888 CLI_DISCONN exit:0 sig:0 core:0 ret:107 time:2499ms
distccd[13001] (dcc_pump_readwrite) ERROR: unexpected eof on fd5
distccd[13001] (dcc_job_summary) client: xxx.xxx.xxx.xxx:32889 CLI_DISCONN exit:0 sig:0 core:0 ret:107 time:2512ms
any ideas what is going on?
edit: i can compile for x86 and x86_64 quite happily using distcc just not arm for some reason
The cross compiler must
(a) be installed (exactly the same binary, not just the same name/location)
(b) in the search path for distcc
Depending on your system setup (distcc as a daemon, or under inetd) the easiest way to achieve things might be to symlink the binaries into /usr/local/bin for the distcc hosts.