Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am using tcan4x5x driver in Linux kernel v4.14.98, I am facing the below issue
[ 27.788175] tcan4x5x spi0.0: Unsupported version number: 0
[ 28.034275] [<ffff0000087db7f0>] tcan4x5x_can_probe+0x318/0x550
[ 28.085188] [<ffff000009451ecc>] tcan4x5x_can_driver_init+0x18/0x20
[ 28.357443] [<ffff0000087db7f8>] tcan4x5x_can_probe+0x320/0x550
[ 28.408271] [<ffff000009451ecc>] tcan4x5x_can_driver_init+0x18/0x20
[ 28.681485] [<ffff0000087db804>] tcan4x5x_can_probe+0x32c/0x550
[ 28.732311] [<ffff000009451ecc>] tcan4x5x_can_driver_init+0x18/0x20
[ 29.004399] [<ffff0000087db80c>] tcan4x5x_can_probe+0x334/0x550
[ 29.055230] [<ffff000009451ecc>] tcan4x5x_can_driver_init+0x18/0x20
[ 29.088498] tcan4x5x spi0.0: Probe failed, err=-22
[ 29.097673] tcan4x5x: probe of spi0.0 failed with error -22
How I can solve this issue?
Would recommend to enable dynamic debug control and check if any more information you getting about error EINVAl error 22.
echo -n '+p' > /sys/kernel/debug/dynamic_debug/control
unload and load driver again
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 months ago.
The community reviewed whether to reopen this question 10 days ago and left it closed:
Original close reason(s) were not resolved
Improve this question
I encountered as below when executing sudo kubeadm init
Help me~~
$ sudo kubeadm init
[init] Using Kubernetes version: v1.24.1
[preflight] Running pre-flight checks
[WARNING SystemVerification]: missing optional cgroups: blkio
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR CRI]: container runtime is not running: output: E0605 10:35:34.973561 12491 remote_runtime.go:925] "Status from runtime service failed" err="rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService"
time="2022-06-05T10:35:34+09:00" level=fatal msg="getting status of runtime: rpc error: code = Unimplemented desc = unknown service runtime.v1alpha2.RuntimeService"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
work around found here :
https://github.com/containerd/containerd/issues/4581
rm /etc/containerd/config.toml
systemctl restart containerd
kubeadm init
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I have this scenario:
group1
p1
p2
p3
p4
My p1 have numprocs=2, like:
numprocs = 2
process_name = '%(program_name)s_%(process_num)02d'
so I have:
root#28d8dc7bdffd:~# supervisorctl status
group1:'p1_00' RUNNING pid 10442, uptime 0:12:10
group1:'p1_01' RUNNING pid 10433, uptime 0:12:10
group1:p2 RUNNING pid 16290, uptime 0:00:07
p3 RUNNING pid 633, uptime 0:34:33
p4 RUNNING pid 483, uptime 0:35:40
I have to start/stop/restart p1 and it's not working.
I tried:
root#28d8dc7bdffd:~# supervisorctl stop group1:p1:*
group1:p1:*: ERROR (no such process)
root#28d8dc7bdffd:~# supervisorctl stop p1:*
error: <class 'xmlrpclib.Fault'>, <Fault 10: 'BAD_NAME: p1'>: file: /usr/lib/python2.7/xmlrpclib.py line: 794
root#28d8dc7bdffd:~# supervisorctl stop group1:p1*
group1:p1*: ERROR (no such process)
I'm conformed on putting the full name of each worker
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 3 years ago.
Improve this question
I am running supervisord 3.0. My supervisord.conf file looks like this:
[unix_http_server]
file=/var/run/supervisor/supervisor.sock
[supervisord]
logfile=/var/log/supervisord.log
logfile_maxbytes=50MB
logfile_backups=10
loglevel=info
pidfile=/var/run/supervisor/supervisord.pid
minfds=1024
minprocs=200
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
[supervisorctl]
serverurl=unix:///var/run/supervisor/supervisor.sock
[program:p2]
command=...
[program:p1]
command=...
[group:myprograms]
programs=p1,p2
Using supervisordctl I can restart both programs individually.
$ supervisorctl restart p1
$ supervisorctl restart p2
However, attempting to restart the group results in an error.
$ supervisorctl restart myprograms:
error: <class 'xmlrpclib.Fault'>, <Fault 10: 'BAD_NAME: myprograms'>: file: /usr/local/lib/python2.7/xmlrpclib.py line: 799
How can I restart the group?
It turns out this was caused by a typo in my config file.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 years ago.
Improve this question
I'm trying to add Facebook API on my web application..
But when I tried to post links using the Graph API.. I got this error:
Fatal error: Uncaught exception 'Facebook\FacebookSDKException' with
message 'couldn't connect to host' in
/home/u614270703/public_html/test/vendor/facebook/php-sdk-v4/src/Facebook/HttpClients/FacebookCurlHttpClient.php:156
Stack trace: #0
/home/u614270703/public_html/test/vendor/facebook/php-sdk-v4/src/Facebook/FacebookRequest.php(248):
Facebook\HttpClients\FacebookCurlHttpClient->send('https://graph.f...',
'POST', Array) #1 /home/u614270703/public_html/test/session2.php(32):
Facebook\FacebookRequest->execute() #2 {main} thrown in
/home/u614270703/public_html/test/vendor/facebook/php-sdk-v4/src/Facebook/HttpClients/FacebookCurlHttpClient.php
on line 156
I don't have any idea what is going on. What does this error means? I don't know why I can't 'connect to host'.
Your server probably blocks outgoing CURL requests, contact your provider and ask him if he could open access to the Facebook API server (graph.facebook.com).
There are other threads about this too:
Fatal error: Uncaught CurlException: 7: couldn't connect to host thrown in ....src/base_facebook.php on line 887
How to resolve cURL Error (7): couldn't connect to host?
https://stackoverflow.com/questions/9425406/facebook-api-exception-object-error-on-facebook-app
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am trying to set up Message archiving for my ejabberd server. I tried to add new module mod_archive following the link http://lboynton.com/2009/11/25/ejabberd-mod_archive-with-mysql-on-ubuntu/. After that i am not able to restart ejabberd server and gives me the following error in ejabberd.log
=ERROR REPORT==== 2010-11-16 12:44:41 ===
E(<0.38.0>:ejabberd_rdbms:67) : Start of supervisor ejabberd_odbc_sup_localhost failed:
{error,{shutdown,{child,undefined,ejabberd_odbc_sup_localhost,
{ejabberd_odbc_sup,start_link,["localhost"]},
transient,infinity,supervisor,
[ejabberd_odbc_sup]}}}
Thanks,
Sathi.
All internet tutorials about mod_archive in Ejabberd are incomplete or very caotics. Or maybe are old. So my problem is I am using Ubuntu 12.04 server LTS with Mysql. And I did all the things that are explained in all blogs.
So to install mod_archive I need to do this:
The typical:
svn co https://svn.process-one.net/ejabberd-modules
cd ejabberd-modules/mod_archive/trunk
./build.sh
cp ebin/*modules in EJABBERD
and configure /etc/ejabberd.cfg
but with this methods EJABBERD does not work.
So I discover that we need to compile other MODULE that are not explained in any site. The module is called CONN_MYSQL
And we can get in the same ejabber-modules dowloaded. So in SVN (https://svn.process-one.net/ejabberd-modules) there are
cd ejabberd-modules/mysql/trunk
./build.sh
cp ebin/*modules in EJABBERD
And work.....
I need a lot of hours to discover this.
I can not use this line configuration in ejabberd.cfg: {odbc_server, "DSN=ejabberd;UID=ejabberd;PWD=ejabberd"} because aplication crashes and says this:
=ERROR REPORT==== 2012-11-28 18:01:08 ===
E(<0.437.0>:mod_archive_odbc:867) : should_store_jid failed: {xmlelement,
"error",
[{"code","500"},
{"type",
"wait"}],
[{xmlelement,
"internal-server-error",
[{"xmlns",
"urn:ietf:params:xml:ns:xmpp-stanzas"}],
[]}]}
So I use this line in ejabberd.cfg:
{odbc_server, {mysql, "server", "database", "username", "password"}}.
and this line into the modules configuration:
{mod_archive_odbc, [{database_type, "mysql"}, {default_auto_save, true}, {enforce_default_auto_save, true}]},
So now works!
I don't remmember if i use
trunk or branches/ejabberd-2.0.x in Emakefile . You could try one and if not works you could try the other.
Ah! and remmember to compile with
./configure --enable-odbc the ejabberd source code.
You can get this in
wget http://www.process-one.net/en/ejabberd/ejabberd/2.1.11/ejabberd-2.1.11.tgz
maybe it is necessary this packages:
apt-get install iodbc libmyodbc
I used this one without any errors: http://www.ndl.kiev.ua/content/mod_archive_odbc-release