I have downloaded cups source with apt-get source cups, and I am trying to compile it with dpkg-buildpackage. The compilation fails with following error:
PASS: All job control files purged.
PASS: Printer 'Test1' correctly produced 55 page(s).
PASS: Printer 'Test2' correctly produced 23 page(s).
PASS: 135 requests logged.
PASS: CUPS-Get-Default not logged.
PASS: 0 emergency messages.
PASS: 0 alert messages.
PASS: 0 critical messages.
FAIL: 19 error messages, expected 18.
E [16/Oct/2014:15:48:55.461975 +0200] Returning IPP client-error-bad-request for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.462540 +0200] Missing attributes-natural-language attribute
E [16/Oct/2014:15:48:55.462577 +0200] Missing printer-uri, job-uri, or ppd-name attribute
E [16/Oct/2014:15:48:55.462651 +0200] Returning IPP client-error-bad-request for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.463161 +0200] Missing attributes-charset attribute
E [16/Oct/2014:15:48:55.463192 +0200] Missing attributes-natural-language attribute
E [16/Oct/2014:15:48:55.463228 +0200] Missing printer-uri, job-uri, or ppd-name attribute
E [16/Oct/2014:15:48:55.463303 +0200] Returning IPP client-error-bad-request for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.463831 +0200] Missing attributes-charset attribute
E [16/Oct/2014:15:48:55.463862 +0200] Missing attributes-natural-language attribute
E [16/Oct/2014:15:48:55.463898 +0200] Missing printer-uri, job-uri, or ppd-name attribute
E [16/Oct/2014:15:48:55.463981 +0200] Returning IPP client-error-bad-request for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.464499 +0200] Missing printer-uri, job-uri, or ppd-name attribute
E [16/Oct/2014:15:48:55.464590 +0200] Returning IPP client-error-bad-request for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.465803 +0200] Returning IPP client-error-bad-request for Get-Jobs (ipp://localhost:8631/jobs) from localhost
E [16/Oct/2014:15:48:55.466380 +0200] Returning IPP server-error-version-not-supported for Get-Jobs (no URI) from localhost
E [16/Oct/2014:15:48:55.522710 +0200] Returning IPP client-error-bad-request for Print-Job (ipp://localhost:8631/printers/Test1) from localhost
E [16/Oct/2014:15:49:02.558807 +0200] Returning IPP client-error-too-many-subscriptions for Create-Printer-Subscription (ipp://localhost:8631/printers/Test1) from localhost
E [16/Oct/2014:15:49:13.164121 +0200] [cups-deviced] PID 8234 (usb) crashed on signal 11!
E [16/Oct/2014:15:49:13.164484 +0200] [cups-deviced] PID 8235 (snmp) stopped with status 1!
PASS: 9 warning messages.
PASS: 0 notice messages.
PASS: 787 info messages.
PASS: 9755 debug messages.
PASS: 19774 debug2 messages.
1 tests failed.
Log files can be found in /tmp/cups-martin/log.
A HTML report was created in /tmp/cups-martin/cups-str-1.5-2014-10-16-martin.html.
Copies of the error_log and cups-str-1.5-2014-10-16-martin.html files are in
/home/martin/src/debian/cups-1.5.3/test.
make[1]: *** [check] Error 1
make[1]: Leaving directory `/home/martin/src/debian/cups-1.5.3'
make: *** [debian/stamp-makefile-check] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
I have no idea what is wrong. I have all build-dependencies installed.
I am using Debian Wheezy
Can somebody please help?
apt-get build-dep cups should be run to get all the build dependencies for cups. I know you say you installed all the dependencies, but since you didn't say how you did it I provide that command as the mechanism I'd use to do it.
A number of things come to mind. Some packages don't build well when done as the root user (you won't find an official source that says it, but I have made that observation over years of building packages on Debian). Generally I do software builds as a normal user but using fakeroot. Since I prefer to use fakeroot for package builds I make sure fakeroot is installed via apt-get install fakeroot. Then as a non-root user I would do apt-get source cups followed by a typical dpkg-buildpackage -b -us -uc -rfakeroot to build binaries on a Debian system. I happened to build Cups 1.5.3 on my Debian Wheezy system here without any issues as a non-root user.
I happened to try this build as root and interestingly enough cups got stuck during the tests while trying to launch the scheduler. This problem didn't exist as a non-root user. Although what happened on my system didn't generate the same resulting error, as my tests would never finish at all!
I'd recommend trying a build using fakeroot as a non-root user if you aren't already doing so.
Specific to your debug output I find this curious:
[cups-deviced] PID 8234 (usb) crashed on signal 11!
I'm wondering if during the tests a problem with a USB printer device is causing your failure. Do you have a USB printer connected directly to your system? If so, try disconnecting it and doing a build. I'm wondering if a problem in the cups-device subsystem specific to a particular USB printer is causing this failure during a cups build.
I happened to find this bug report regarding a similar problem with cups-device and signal 11 (on an older Ubuntu - Debian based system). It is an older bug that was apparently fixed, but I wonder if there are other cases that are still a problem. The bug had this to say:
But, for some reason or another, Ubuntu 9.10 and 10.04 does not properly recognize the existence of USB printers anymore. It does not recognize my HP Laserjet 4 and probably fails to recognize other USB printers, too.
It then provides this in the error log which is similar to the errors you are seeing during the tests while building cups:
Architecture: amd64
CupsErrorLog:
E [18/Apr/2010:09:43:44 -0600] [cups-deviced] PID 1768 (usb) crashed on signal 11!
E [18/Apr/2010:09:46:36 -0600] [cups-deviced] PID 1817 (usb) crashed on signal 11!
While I can't tell you what exactly is wrong I can point you in the right direction.
What you see there is the failing of the unit test for the ipptool.
You might want to investigate this further, perhaps starting with this link
Related
I have remote linux server and I am trying to build jenkins image from Dockerfile.
As I mounting local folder to the image, jenkins is not able to install necessary plugins.
I follow the advices from Official Jenkins Image: Installing more tools.
During building process I get an error:
=> ERROR [3/3] RUN /usr/local/bin/plugins.sh /usr/share/jenkins/plugins.txt------> [3/3] RUN /usr/local/bin/plugins.sh /usr/share/jenkins/plugins.txt:
#0 0.292 WARN: plugins.sh is deprecated, please switch to install-plugins.sh
#0 0.293 Analyzing war: /usr/share/jenkins/jenkins.war
#0 0.451 Downloading cloudbees-folder:6.9
#0 0.460 **curl: (3) Illegal characters found in URL**
Dockerfile:3
1 | FROM jenkins:2.60.3
2 | COPY plugins.txt /usr/share/jenkins/plugins.txt
3 | >>> RUN /usr/local/bin/plugins.sh /usr/share/jenkins/plugins.txt*
here is my content of plugins.txt file:
cloudbees-folder:6.9
antisamy-markup-formatter:2.7
build-timeout:1.28
credentials-binding:1.27.1
timestamper:1.21
ws-cleanup:0.44
ant:1.13
gradle:2.2
workflow-aggregator:2.7
github-branch-source:2.11.5
pipeline-github-lib:36.v4c01db_ca_ed16
pipeline-stage-view:2.31
git:5.0.0
subversion:2.17.0
ssh-slaves:2.854.v7fd446b_337c9
matrix-auth:3.1.6
pam-auth:1.10
ldap:659.v8ca_b_a_fe79fa_d
email-ext:2.93
mailer:1.34.2
I found one possible solution saying that Docker Jenkins Image - curl: (3) Illegal characters found in URL
there is different line endings between Windows and Mac OS.
however it did not help me. I would wait for your suggestions.
On running command solana-test-validator on windows system, getting an error
[2022-01-06T06:54:41.602352800Z INFO solana_test_validator] solana-validator 1.9.0 (src:7782d34b; feat:378846963)
[2022-01-06T06:54:41.602479300Z INFO solana_test_validator] Starting validator with: ArgsOs {
inner: [
"solana-test-validator",
],
}
[2022-01-06T06:54:41.602617400Z WARN solana_perf] CUDA is disabled
[2022-01-06T06:54:41.602720300Z INFO solana_perf] AVX detected
[2022-01-06T06:54:41.602823600Z INFO solana_perf] AVX2 detected
[2022-01-06T06:54:41.606436300Z INFO solana_faucet::faucet] Faucet started. Listening on: 0.0.0.0:9900
[2022-01-06T06:54:41.606635600Z INFO solana_faucet::faucet] Faucet account address: 2P4mpwfirxqrL3naJD7C5UHYynPgVugaRu9sBT6m73EZ
Ledger location: test-ledger
Log: test-ledger\validator.log
⠁
⠉ Initializing...
[2022-01-06T06:54:44.975790700Z INFO solana_ledger::blockstore] "test-ledger\\rocksdb" open took 3.3s
[2022-01-06T06:54:44.981740300Z INFO solana_metrics::metrics] metrics disabled: SOLANA_METRICS_CONFIG: environment variable not found
[2022-01-06T06:54:44.982273700Z INFO solana_metrics::metrics] datapoint: shred_insert_is_full total_time_ms=0i slot=0i ⠒ Initializing...
[2022-01-06T06:54:45.595853800Z ERROR solana_ledger::blockstore] tar stdout:
[2022-01-06T06:54:45.596099200Z ERROR solana_ledger::blockstore] tar stderr: tar: Can't launch external program: bzip2
Error: failed to start validator: Failed to create ledger at test-ledger: blockstore error```
This is a current annoyance with natively using Windows with solana-test-validator. It shells out to tar with bzip2, which isn't available in the default Windows shell.
As a workaround, try installing Git BASH and then running solana-test-validator from a Git BASH shell.
Source code for the issue can be found at: https://github.com/solana-labs/solana/blob/f1e2598baa80a0ad4e8450c8b5e3c5ab164f501c/ledger/src/blockstore.rs#L3789-L3814 -- the j flag indicates to use bzip2
I have tried the solutions I found online for this, but none of them seem to work...
Even after installing blogdown from github and updating hugo, I get a timeout error.
remotes::install_github('rstudio/blogdown')
blogdown::update_hugo()
That is, when I run blogdown::serve_site I get this error:
Launching the server via the command: C:\Users\Master\AppData\Roaming\Hugo\hugo.exe server --bind 127.0.0.1 -p 4321 --themesDir themes -t hugo-future-imperfect -D -F --navigateToChanged ERROR: The process "10244" not found. Error: It took more than 30 seconds to launch the server. There may be something wrong. The process has been killed. If the site needs more time to be built and launched, set options(blogdown.server.timeout) to a larger value.
Is there another way to fix this?
What is causing this error?
Thanks!
I have the same problem on Kubuntu 20.10. I installed latest blogdown and hugo serveral days ago. I have blogdown 0.21.47 and hugo 0.79.0 on Kubuntu. Finally, I found a method to fix it.
Close Rstudio
Open terminal
Enter directory of your website
Execute hugo server -D
Press Ctrl C to stop
Open Rstudio
Click Addin -> BLOGDOWN -> Serve Site
I don't know why it works or whether it works in your case. Please test it and let us know whether it works.
I am running into the same problem.
blogdown::serve_site()
wont work:
Error: It took more than 30 seconds to launch the server. An error might have occurred with hugo. You may run blogdown::build_site() and see if it gives more info. If the site is very large and needs more time to be built, set options(blogdown.server.timeout) to a larger value.
although blogdown::build_site() works smoothly. The blogdown::serve_site() function works fine for a newly created project/website.
For repository see here.
Not sure if it is a blogdown, hugo or academic theme issue.
sessionInfo()
R version 4.0.3 (2020-10-10)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 17763)
Matrix products: default
locale:
[1] LC_COLLATE=Dutch_Netherlands.1252 LC_CTYPE=Dutch_Netherlands.1252
[3] LC_MONETARY=Dutch_Netherlands.1252 LC_NUMERIC=C
[5] LC_TIME=Dutch_Netherlands.1252
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] servr_0.20
loaded via a namespace (and not attached):
[1] Rcpp_1.0.5 rstudioapi_0.13 knitr_1.30 magrittr_2.0.1 mnormt_2.0.2 pbivnorm_0.6.0
[7] R6_2.5.0 rlang_0.4.9 tools_4.0.3 tmvnsim_1.0-2 xfun_0.19 htmltools_0.5.0
[13] yaml_2.2.1 digest_0.6.27 lavaan_0.6-7 bookdown_0.21 processx_3.4.5 later_1.1.0.1
[19] promises_1.1.1 ps_1.4.0 evaluate_0.14 rmarkdown_2.5 blogdown_0.21.50 compiler_4.0.3
[25] stats4_4.0.3 jsonlite_1.7.1 httpuv_1.5.4
I had the same problem on. Installing "go" (https://golang.org/doc/install) helped - this was missing after my clean install of big sur.
I have a problem with run my c++ tensorflow app directly after reboot ubuntu.
normally I build app by bazel build
bazel build -c opt --local_resources 3072,4.0,1.0 --verbose_failures --config=monolithic //tensorflow/app/...
after build, when I execute
bazel-bin/tensorflow/app/run
everything is work perfectly but, when I reboot ubuntu and execute firstly bazel-bin I have spam of this errors.
May 11 12:29:05 tegra-ubuntu start.sh[800]: 2018-05-11 12:29:04.622723: E tensorflow/stream_executor/cuda/cuda_driver.cc:967] failed to alloc 2304 bytes on host: CUDA_ERROR_UNKNOWN
May 11 12:29:05 tegra-ubuntu start.sh[800]: 2018-05-11 12:29:04.622849: E tensorflow/stream_executor/cuda/cuda_driver.cc:967] failed to alloc 2304 bytes on host: CUDA_ERROR_UNKNOWN
I guess that is a problem in loaded packages. When bazel build is executing before bazel-run, loading packages is correct.
There is a way to only load missing packages without earlier building? I need to run app immediately after start but my building process is to long to building before run app
Solution:
SessionOptions opts;
opts.config.mutable_gpu_options()->set_allow_growth(true);
session->reset(tensorflow::NewSession(opts));
Does enabling gpu_options.allow_growth fix the problem?
https://devtalk.nvidia.com/default/topic/1029742/tensorflow-1-6-not-working-with-jetpack-3-2/
I am using a module called pymatgen (http://pymatgen.org). There is a function within pymatgen
which displayed a graphical representation of an structure object. pymatgen requires VTK and
the VTK python bindings. I have installed both on my CentOS 7 system. Yum reports
%yum list installed |grep -i vtk vtk.x86_64
6.1.0-5.el7 #epel vtk-python.x86_64
6.1.0-5.el7 #epel vtk-qt.x86_64
6.1.0-5.el7#epel vtk-qt-python.x86_64#epel
in ipython (4.2.1)
In [1]: import pymatgen as mg
In [2]: from pymatgen.vis.structure_vtk import StructureVis
In [3]: struct = mg.Structure.from_file('POSCAR')
In [4]: StructureVis(struct)
libGL error: No matching fbConfigs or visuals found libGL error:
failed to load driver: swrast
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 150 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 44
Current serial number in output stream: 45
I am confused by this error as VTK is installed. I am using the CentOS 7 machine via a
remote X11 client (on a Macintosh using Mac OS X 10.11.5).
Does anyone have a suggestion as to how to resolve this problem as it is preventing me from using the visualization environment.