To reproduce:
Have corrupted database (I think it's the same-time writing issue for non waitForSync collection)
Use arangodump.exe
Use arangorestore.exe (Service arangod.exe stops working while run)
Get Arangod.exe crashed after trying to launch the service
To make backup I were ignoring some collection using --maskings option and rule set. I have gotten an error if I weren't.
To restore the data I did use stable and also nightly, the latest versions of ArangoDB server.
There is not much useful info for the deeper log level.
Also happens for another win10 computer. And can't be run on linux (wsl debian) because my computer's processor doesn't support sse 4.2 or higher
Older version 3.8.5-1 works fine! (upgraded my previous version 3.8.1)
Related
I was trying to install SDK and Emulator without the Andriod studio on Ubuntu 20.04.
But got stuck at this error.
E0520 11:06:29.866803544 5261 socket_utils_common_posix.cc:201] check for SO_REUSEPORT: {"created":"#1589952989.866791260","description":"SO_REUSEPORT unavailable on compiling system","file":"/mnt/tmpfs/src/android/emu-master-dev/external/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":169}
checkValid: hw configs not eq
I got the solution from this article:
So in order to fix this, I just disabled the Camera by switching the option from Emulated to None and that was all.
Don't ask why this works, but it seemed to solve it for me.
Install Android SDK Platform tools. if already exist uninstall and install Android SDK Platform tool in ubuntu 20.04
Seems a GPU issue, try :
sudo ubuntu-drivers autoinstall
Or (or both) change graphic emulated performance to software if your emulated device allow it.
Had same issue with linux mint android studio ..
Hope it will help.
Though not directly affected by the error you described, when stuck at this point (namely, when supposed to be connecting back to the ADB server, but can't), this can be a result of a corrupted quick-boot snapshot.
What worked for me is to hard-delete the existing quick-boot snapshot, and have the emulator regenerate it on the next run.
To delete the snapshots:
rm -fr ~/.android/avd/<AVD name>/snapshots/default_boot
To regenerate the next snapshot, rerun the emulator as you normally would, then kill it after if full loads. But first, make sure that it is configured for saving a quick-boot snapshot on exit:
Edit quickbootChoice.ini, for example:
vi ~/.android/avd/<AVD name>/quickbootChoice.ini
The only line there should be:
saveOnExit = true
If you wish to see whether any of this is likely to help you before making any changes, run the emulator with the -no-snapshot argument applied, beforehand. For example:
$ANDROID_SDK_ROOT/emulator/emulator -no-snapshot #Pixel_API_29 &
(Or find a way to do this through Android Studio)
A note regarding other answers here that advised configuring the camera differently (which seems unrelated): It is very likely that changing the camera setting, for the Emulator, is considered a configuration change - which ends up in forcing a cold-boot (i.e. skipping usage of the quick-boot snapshot), which can explain why it works (but with no voodoo involved).
I was about to install node.js on a brand new Windows 7 64bit system. But during the installation I get a bluescreen. It happens while "copying new files". I tried node.js 8.9.4 and 9.5.0, both in 64 bit. Any idea what's wrong?
edit: I now enabled virtual memory and the message has changed. Now I get
The driver is attempting to access memory beyond the end of the allocation.
And here the current screenshot of the dump:
Honestly, these problems seem absolutely weird... I have never before had such issues with the installation of nodejs. And I'm doing it on a new machine which is up-to-date.
I've figured out what the issue was. It had to do with Comodo Programs Manager. After having deinstalled the program, everything worked fine again. But on my old machine I used to run Comodo Programs Manager as well. So it remains strange why it now caused such issues.
I've just downloaded Eclipse on elementary OS and attempted to launch it. After doing so, I saw the loading screen for a few seconds before it disappeared and left me with the desktop. Since then, my computer (an old Dell with 4GB of RAM and an Intel Core Duo) has been very unresponsive and the disk activity indicator is almost constantly lit up. I've been looking at the desktop for around 30 minutes now! How can I solve this problem and launch Eclipse?
EDIT: Running eclipse -clean from the command line produces the following error: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
First, you might review your installation steps. If nothing is obviously wrong, check the following:
check for any error logs
check that you're using the proper Java version
make sure that there's enough memory allocated for Eclipse (see the eclipse.ini file)
as a last resort, try reinstalling it
See also the following guide for installing on Elementary OS: how to install
If that's not working submit more details of your specific problems.
NOTE: You may have to find the right Java and install it "by hand" rather than relying upon the distribution's package manager. You can "point" Eclipse at the right Java by editing the .ini file.
Some related links are as follows:
a similar symptom related to multiple screens and/or corrupt workspace
General trouble-shooting related to your issue and symptoms
Our main client server is running MySQL 5.0.96, but we'd like to upgrade to 5.1. We're running a couple of older EE1.6 sites (non older than 1.6.7 iirc), and the rest are EE2.2+
Are there any gotchas/problems we might encounter (maybe in our custom self-wrriten add-ons) when we upgrade?
Thanks!
I run many EE installs with MySQL 5.1+ clients with no issues. Unless your SQL in custom add-on is really sloppy and you're running MySQL in STRICT mode, I can't see any issues.
My production server runs 5.1 and both my local and dev servers run 5.5 without issue, so I doubt you'll run into any problems.
Currently running 5.5.28 without any problem.
Moving from XP to Windows 7 with client side.
Running into a couple issues with Sybase 15.
1) "Interactive SQL" - many widgets in ie options are defective or missing
2) When running simple query get Swing/AVT widget exception error.
Anyone ran into or worked thru any issues moving to 7?
Other versions of the Windows app, but not 7. As you may be aware 7 is only slightly more reliable than Vista.
Those messages are classically due to (a) Sybase Client (SybaseCentral; InteractiveSQL, the GUI utilities) all using the Java VM and (b) that not being successfuly installed.
Get the Sybase Client CD, and install again. Do not Customise, use the Default installation options. Watch the progress for errors. Ensure the JVM installation succeeds. You may have to retrieve any missing files from the Windows 7 CD.
Otherwise open a Support Case.