when i have installed Miktex and update, i type "latex -v" in cmd and found error:
Sorry, but latex did not succeed.The log file hopefully contains the information to get MiKTeX going again:C:\Users\10950\AppData\Local\MiKTeX\miktex\log\latex.log
and in my latex.log i found this:
2021-12-15 17:23:14,228+0800 INFO latex - this process (38868) started by 'cmd' with command line: latex -v
2021-12-15 17:23:14,232+0800 INFO latex - this is MiKTeX-PDFTEX 4.10.0 (1.40.24) (MiKTeX 21.12.10)
2021-12-15 17:23:14,236+0800 INFO latex - allowing known shell commands
2021-12-15 17:23:14,260+0800 FATAL latex.core - The command line options could not be processed.
2021-12-15 17:23:14,260+0800 FATAL latex.core - Data: optionError="unknown option"
2021-12-15 17:23:14,260+0800 FATAL latex.core - Source: Libraries\MiKTeX\TeXAndFriends\webapp.cpp:397
2021-12-15 17:23:14,260+0800 FATAL latex - The command line options could not be processed.
2021-12-15 17:23:14,260+0800 FATAL latex - Info: optionError="unknown option"
2021-12-15 17:23:14,260+0800 FATAL latex - Source: Libraries\MiKTeX\TeXAndFriends\webapp.cpp
2021-12-15 17:23:14,260+0800 FATAL latex - Line: 397
2021-12-15 17:23:14,263+0800 INFO latex - this process (38868) finishes with exit code 1
how to fix this ,thanks
Related
I'm running WebStorm 2022.2.2 on Windows and my Node.js project is sitting in WSL2 Ubuntu distribution, and I'm trying to get the debugger working for my setup with no success so far.
This is the error popping up as soon as I press the debug button:
2022-09-24 11:38:49,751 [61701563] INFO - #c.i.j.d.JavaScriptDebugProcess - JSDebugger publish port: 58315
2022-09-24 11:38:49,861 [61701673] INFO - #c.i.e.r.ExecutionUtil - Error running 'my-project:dev':<br>Failed to prepare environment: File is not executable: /mnt/c/Users/MyPC/AppData/Local/JetBrains/Toolbox/apps/WebStorm/ch-0/222.4167.31/bin/wslproxy (C:\Users\MyPC\AppData\Local\JetBrains\Toolbox\apps\WebStorm\ch-0\222.4167.31\bin\wslproxy)
com.intellij.execution.ExecutionException: Failed to prepare environment: File is not executable: /mnt/c/Users/MyPC/AppData/Local/JetBrains/Toolbox/apps/WebStorm/ch-0/222.4167.31/bin/wslproxy (C:\Users\MyPC\AppData\Local\JetBrains\Toolbox\apps\WebStorm\ch-0\222.4167.31\bin\wslproxy)
at com.intellij.javascript.nodejs.execution.NodeTargetRun.prepareCommandLine(NodeTargetRun.kt:129)
at com.intellij.javascript.nodejs.execution.NodeTargetRun.startProcessEx(NodeTargetRun.kt:138)
at com.intellij.javascript.nodejs.execution.NodeTargetRun.startProcess(NodeTargetRun.kt:103)
at com.github.iguissouma.nxconsole.buildTools.rc.NxRunProfileState.startProcess(NxRunProfileState.kt:70)
at com.intellij.javascript.nodejs.execution.NodeBaseRunProfileState$Companion.runInBackground(NodeBaseRunProfileState.kt:58)
at com.intellij.javascript.nodejs.execution.NodeBaseRunProfileState$Companion.access$runInBackground(NodeBaseRunProfileState.kt:41)
at com.intellij.javascript.nodejs.execution.NodeBaseRunProfileState$Companion$executeUnderProgress$1.run(NodeBaseRunProfileState.kt:49)
at com.intellij.openapi.progress.impl.CoreProgressManager.startTask(CoreProgressManager.java:442)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.startTask(ProgressManagerImpl.java:114)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsynchronously$5(CoreProgressManager.java:493)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$3(ProgressRunner.java:252)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:188)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$12(CoreProgressManager.java:608)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:683)
at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:639)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:607)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:60)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:175)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:252)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.Exception: File is not executable: /mnt/c/Users/MyPC/AppData/Local/JetBrains/Toolbox/apps/WebStorm/ch-0/222.4167.31/bin/wslproxy (C:\Users\MyPC\AppData\Local\JetBrains\Toolbox\apps\WebStorm\ch-0\222.4167.31\bin\wslproxy)
at com.intellij.execution.wsl.WslToolsKt.getTool(WslTools.kt:17)
at com.intellij.execution.wsl.WslProxy.<init>(WslProxy.kt:101)
at com.intellij.execution.wsl.target.WslTargetEnvironment.getWslPort(WslTargetEnvironment.kt:88)
at com.intellij.execution.wsl.target.WslTargetEnvironment.<init>(WslTargetEnvironment.kt:79)
at com.intellij.execution.wsl.target.WslTargetEnvironmentRequest.prepareEnvironment(WslTargetEnvironmentRequest.kt:68)
at com.intellij.javascript.nodejs.execution.NodeTargetRun.prepareCommandLine(NodeTargetRun.kt:122)
... 26 more
Caused by: com.intellij.execution.wsl.ProcessExistedNotZeroException: Can't execute test -x /mnt/c/Users/MyPC/AppData/Local/JetBrains/Toolbox/apps/WebStorm/ch-0/222.4167.31/bin/wslproxy: 1.
at com.intellij.execution.wsl.WslProcessToolsKt.waitProcess(WslProcessTools.kt:37)
at com.intellij.execution.wsl.WslProcessToolsKt.runCommand(WslProcessTools.kt:19)
at com.intellij.execution.wsl.WslProcessToolsKt.runCommand$default(WslProcessTools.kt:14)
at com.intellij.execution.wsl.WslToolsKt.getTool(WslTools.kt:14)
... 31 more
What do I have to do in order to get the Debugger working?
I have a simple 3 node cluster with some sample data. I want to take backup (To S3) of the cluster and restore it in different cluster.
I can take node backup and restore however cluster level backup never seems to be working. It is throwing the following error.
Cassandra version - 3.10, OS - Amazon linux 2 - centos
[2022-05-20 06:37:20,534] INFO: Creating snapshots on all nodes
[2022-05-20 06:37:20,534] INFO: Executing "nodetool -Dcom.sun.jndi.rmiURLParsing=legacy snapshot -t medusa-samp" on following nodes ['nodecassandra-2.localdomain', 'nodecassandra-3.localdomain', 'nodecassandra-1.localdomain'] with a parallelism/pool size of 500
[2022-05-20 06:37:21,129] ERROR: Job executing "nodetool -Dcom.sun.jndi.rmiURLParsing=legacy snapshot -t medusa-samp" ran and finished with errors on following nodes: ['nodecassandra-1.localdomain', 'nodecassandra-2.localdomain', 'nodecassandra-3.localdomain']
[2022-05-20 06:37:21,130] INFO: [nodecassandra-2.localdomain] [err] /bin/bash: nodetool: command not found
[2022-05-20 06:37:21,130] INFO: nodecassandra-2.localdomain-stderr: /bin/bash: nodetool: command not found
[2022-05-20 06:37:21,130] INFO: [nodecassandra-3.localdomain] [err] /bin/bash: nodetool: command not found
[2022-05-20 06:37:21,130] INFO: nodecassandra-3.localdomain-stderr: /bin/bash: nodetool: command not found
[2022-05-20 06:37:21,130] INFO: [nodecassandra-1.localdomain] [err] /bin/bash: nodetool: command not found
[2022-05-20 06:37:21,130] INFO: nodecassandra-1.localdomain-stderr: /bin/bash: nodetool: command not found
[2022-05-20 06:37:21,130] ERROR: Some nodes failed to create the snapshot.
[2022-05-20 06:37:21,130] ERROR: This error happened during the cluster backup: Some nodes failed to create the snapshot.
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/medusa/backup_cluster.py", line 64, in orchestrate
backup.execute(cql_session_provider)
File "/usr/local/lib/python3.7/site-packages/medusa/backup_cluster.py", line 146, in execute
self._create_snapshots()
File "/usr/local/lib/python3.7/site-packages/medusa/backup_cluster.py", line 163, in _create_snapshots
raise Exception(err_msg)
Exception: Some nodes failed to create the snapshot.
[2022-05-20 06:37:21,131] ERROR: Something went wrong! Attempting to clean snapshots and exit.
[2022-05-20 06:37:21,131] INFO: Executing "nodetool -Dcom.sun.jndi.rmiURLParsing=legacy clearsnapshot -t medusa-samp" on following nodes ['nodecassandra-2.localdomain', 'nodecassandra-3.localdomain', 'nodecassandra-1.localdomain'] with a parallelism/pool size of 1
[2022-05-20 06:37:22,290] ERROR: Job executing "nodetool -Dcom.sun.jndi.rmiURLParsing=legacy clearsnapshot -t medusa-samp" ran and finished with errors on following nodes: ['nodecassandra-1.localdomain', 'nodecassandra-2.localdomain', 'nodecassandra-3.localdomain']
[2022-05-20 06:37:22,290] INFO: [nodecassandra-2.localdomain] [err] /bin/bash: nodetool: command not found
[2022-05-20 06:37:22,290] INFO: nodecassandra-2.localdomain-stderr: /bin/bash: nodetool: command not found
[2022-05-20 06:37:22,290] INFO: [nodecassandra-3.localdomain] [err] /bin/bash: nodetool: command not found
[2022-05-20 06:37:22,290] INFO: nodecassandra-3.localdomain-stderr: /bin/bash: nodetool: command not found
[2022-05-20 06:37:22,290] INFO: [nodecassandra-1.localdomain] [err] /bin/bash: nodetool: command not found
[2022-05-20 06:37:22,290] INFO: nodecassandra-1.localdomain-stderr: /bin/bash: nodetool: command not found
[2022-05-20 06:37:22,291] ERROR: Some nodes failed to clear the snapshot. Cleaning snapshots manually is recommended
I have added path variables for cassandra bin, nodetool.
Added CASSANDRA_HOME, CASSANDRA_CONF in /etc/profile.d/cassandra.sh.
Added ssh details in medusa.ini. Provided cassandra_conf file path,
storage (s3) details and ssh details in medusa.ini.
Am i missing anything else ?
[Question posted by a user on YugabyteDB Community Slack]
Debug build does not seem to be working in the clang12 based build:
./yb_build.sh debug --sj
[100%] Linking CXX executable ../../../tests-integration-tests/cdc_service-int-test
[100%] Built target cdc_service-int-test
make: *** [Makefile:101: all] Error 2
real 0m28.279s
user 4m4.235s
sys 0m25.477s
[2022-02-26T15:52:32 yb_build.sh:466 run_cxx_build] C++ build finished with exit code 2 (build type: debug, compiler: clang12). Timing information is available above.
==========================================================================================
YUGABYTE BUILD SUMMARY
==========================================================================================
Build type : debug
C/C++ compiler : clang12
Build architecture : x86_64
Build directory : /yb-source/build/debug-clang12-dynamic
Third-party dir : /opt/yb-build/thirdparty/yugabyte-db-thirdparty-v20211222064150-dd4872fe56-almalinux8-x86_64-clang12
C++ compilation time : 28 seconds
Exit code : 2
------------------------------------------------------------------------------------------
doing
./yb_build.sh debug --clang12 --sj
also results in an error
...
[m-1] In YugabyteDB, setting LC_COLLATE to C and all other locale settings to en_US.UTF-8 by default. Locale support will be enhanced as part of addressing https://github.com/yugabyte/yugabyte-db/issues/1557
[m-1] initdb: invalid locale name "en_US.UTF-8"
[m-1] I0226 15:54:20.630203 15811 pg_wrapper.cc:521] initdb took 124 ms
[m-1] E0226 15:54:20.630272 15811 pg_wrapper.cc:525] initdb failed: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
[m-1] E0226 15:54:20.630429 15811 catalog_manager.cc:7776] initdb failed: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
E0226 15:54:21.075644 15749 external_mini_cluster.cc:1247] master reported an initdb error: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
/yb-source/src/yb/yql/pgwrapper/pg_wrapper_test_base.cc:58: Failure
Failed
Bad status: Runtime error (yb/integration-tests/external_mini_cluster.cc:1248): Failed to start masters.: initdb failed: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
[m-1] W0226 15:54:21.096375 15815 catalog_manager.cc:2084] Tablespace refresh task failed with error Internal error (yb/master/catalog_manager.cc:1929): pg_tablespace table info not found
Test failure stack trace:
/yb-source/src/yb/yql/pgwrapper/pg_wrapper_test_base.cc:58: # 0x7f2962b044e9 yb::pgwrapper::PgWrapperTestBase::SetUp()
/yb-source/src/yb/yql/pgwrapper/create_initial_sys_catalog_snapshot.cc:29: # 0x404d94 yb::pgwrapper::CreateInitialSysCatalogSnapshotTest::SetUp()
I0226 15:54:21.706461 15749 external_mini_cluster.cc:2206] { daemon_id: m-1 bound_rpc: :0 } Starting Shutdown()
I0226 15:54:21.706606 15749 external_mini_cluster.cc:2249] Killing /yb-source/build/debug-clang12-dynamic/tests-pgwrapper/../bin/yb-master with pid 15756 with SIGKILL
I0226 15:54:21.719123 15749 test_util.cc:94] -----------------------------------------------
I0226 15:54:21.719149 15749 test_util.cc:95] Had fatal failures, leaving test files at /tmp/yb_test.tmp.32433.7631.5669.pid15685/create_initial_sys_catalog_snapshot.CreateInitialSysCatalogSnapshotTest.CreateInitialSysCatalogSnapshot.1645890856672495-15749
[ FAILED ] CreateInitialSysCatalogSnapshotTest.CreateInitialSysCatalogSnapshot (5016 ms)
[----------] 1 test from CreateInitialSysCatalogSnapshotTest (5016 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (5016 ms total)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] CreateInitialSysCatalogSnapshotTest.CreateInitialSysCatalogSnapshot
1 FAILED TEST
I0226 15:54:21.751582 15748 run-with-timeout.cc:198] subprocess.Wait finished, waitpid() returned 256
...
[postprocess_test_result.py:246] 2022-02-26 15:54:22,577 INFO: Wrote JSON test report file: /yb-source/build/debug-clang12-dynamic/yb-test-logs/tests-pgwrapper__create_initial_sys_catalog_snapshot/CreateInitialSysCatalogSnapshotTest_CreateInitialSysCatalogSnapshot_test_report.json
(end of standard error)
Traceback (most recent call last):
File "/yb-source/python/yb/gen_initial_sys_catalog_snapshot.py", line 83, in <module>
main()
File "/yb-source/python/yb/gen_initial_sys_catalog_snapshot.py", line 74, in main
raise RuntimeError("initdb failed in %.1f sec" % elapsed_time_sec)
RuntimeError: initdb failed in 6.4 sec
make[2]: *** [src/yb/yql/pgwrapper/CMakeFiles/initial_sys_catalog_snapshot.dir/build.make:70: src/yb/yql/pgwrapper/CMakeFiles/initial_sys_catalog_snapshot] Error 1
make[1]: *** [CMakeFiles/Makefile2:51929: src/yb/yql/pgwrapper/CMakeFiles/initial_sys_catalog_snapshot.dir/all] Error 2
make: *** [Makefile:101: all] Error 2
This happens in Alma Linux 8.5. Any hints?
You need some additional packages and it should work:
dnf install langpacks-en glibc-all-langpacks -y
I am trying to run a nexflow pipeline on some data via the Linux command line, but when I do so, it fails because it fails to create the Conda environment.
It looks like it tries to run the pipeline anyway, despite the environment not being set up properly, and so generates an error message. Any help would be much appreciated. Here is the error message:
Error executing process > 'my_process (1)'
Caused by:
Failed to create Conda environment
command: conda env create --prefix /my_file_path-6bf38a923b48a255f96ea3d66d372e6c --file /my_file_path/environment.yml
status : 143
message:
Here is my environment.yml file:
name: pipeline_name
channels:
- bioconda
- conda-forge
- defaults
dependencies:
- filtlong
- blast==2.5
- minimap2
- samtools
- pysam
- pandas
- matplotlib
- pysamstats
- seaborn
- medaka
- bedtools
- bedops
- seqtk
- bioawk
- sniffles
Not an answer to this question, but if you get a similar failure with a different exit status (120, not 143), try the fix in this thread. Reposting it here:
conda environment from file not working using nextflow · Issue #1081 · nextflow-io/nextflow: https://github.com/nextflow-io/nextflow/issues/1081
pditommaso commented on Mar 18, 2019
The 120 exit status signals that
it was reached the creation timeout. Try increasing it, eg.
conda.createTimeout = '1 h'
I ran yb-ctl create as specified at https://download.yugabyte.com/local#linux and ran into these errors
13:10 $ bin/yb-ctl create
Creating cluster.
Waiting for cluster to be ready.
Viewing file /net/dev-server-sanketh-3/share/yugabyte-data/node-1/disk-1/tserver.err:
/tmp/pkg1/yugabyte-2.0.7.0/bin/yb-tserver: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
Viewing file /net/dev-server-sanketh-3/share/yugabyte-data/node-1/disk-1/master.err:
/tmp/pkg1/yugabyte-2.0.7.0/bin/yb-master: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
Traceback (most recent call last):
File "bin/yb-ctl", line 1968, in <module>
control.run()
File "bin/yb-ctl", line 1945, in run
self.args.func()
File "bin/yb-ctl", line 1707, in create_cmd_impl
self.wait_for_cluster_or_raise()
File "bin/yb-ctl", line 1552, in wait_for_cluster_or_raise
raise RuntimeError("Timed out waiting for a YugaByte DB cluster!")
RuntimeError: Timed out waiting for a YugaByte DB cluster!
Viewing file /tmp/tmp3NIbj3:
2019-12-06 13:10:18,634 INFO: Starting master-1 with:
/tmp/pkg1/yugabyte-2.0.7.0/bin/yb-master --fs_data_dirs "/net/dev-server-sanketh-3/share/yugabyte-data/node-1/disk-1" --webserver_interface 127.0.0.1 --rpc_bind_addresses 127.0.0.1 --v 0 --version_file_json_path=/tmp/pkg1/yugabyte-2.0.7.0 --webserver_doc_root "/tmp/pkg1/yugabyte-2.0.7.0/www" --callhome_enabled=false --replication_factor=1 --yb_num_shards_per_tserver 2 --ysql_num_shards_per_tserver=2 --master_addresses 127.0.0.1:7100 --enable_ysql=true >"/net/dev-server-sanketh-3/share/yugabyte-data/node-1/disk-1/master.out" 2>"/net/dev-server-sanketh-3/share/yugabyte-data/node-1/disk-1/master.err" &
2019-12-06 13:10:18,658 INFO: Starting tserver-1 with:
/tmp/pkg1/yugabyte-2.0.7.0/bin/yb-tserver --fs_data_dirs "/net/dev-server-sanketh-3/share/yugabyte-data/node-1/disk-1" --webserver_interface 127.0.0.1 --rpc_bind_addresses 127.0.0.1 --v 0 --version_file_json_path=/tmp/pkg1/yugabyte-2.0.7.0 --webserver_doc_root "/tmp/pkg1/yugabyte-2.0.7.0/www" --callhome_enabled=false --tserver_master_addrs=127.0.0.1:7100 --yb_num_shards_per_tserver=2 --redis_proxy_bind_address=127.0.0.1:6379 --cql_proxy_bind_address=127.0.0.1:9042 --local_ip_for_outbound_sockets=127.0.0.1 --use_cassandra_authentication=false --ysql_num_shards_per_tserver=2 --enable_ysql=true --pgsql_proxy_bind_address=127.0.0.1:5433 >"/net/dev-server-sanketh-3/share/yugabyte-data/node-1/disk-1/tserver.out" 2>"/net/dev-server-sanketh-3/share/yugabyte-data/node-1/disk-1/tserver.err" &
2019-12-06 13:10:18,662 INFO: Waiting for master and tserver processes to come up.
2019-12-06 13:10:29,126 INFO: PIDs found: {'tserver': [None], 'master': [None]}
2019-12-06 13:10:29,127 ERROR: Failed waiting for master and tserver processes to come up.
^^^ Encountered errors ^^^
Could you please let me know as to how I could fix this?
Did you run ./bin/post_install.sh from the setup ?
If yes, maybe you're missing apt-get install libatomic1 ?