dnd 5e – How accurate is the knowledge of a casting target to know that it fails?

After reading this question, I remembered a problem with that scrying spell for some time. Specifically, the spell is called:

If a target knows you are casting that spell, it can voluntarily fail the save if it is to be watched.

How detailed does the goal have to be? Is it enough to say, "I'll check you out sometime next year" or does it have to be as detailed as "October 23, 1491 at 12:31:09, I'll look at you"?
If it is not the last one, the target would have to notice that as well something if requested, or alternatively decide to fail all readings against the queries you have made.

How accurate must the knowledge of the goal of your casting be?

ftp – Connection to proFTPd fails with LDAP authentication (no user found)

I have the proftpd server installed and configured with my LDAP. Unfortunately, when I try to connect to filezilla, we will fail with this error:

USER admin: no such found from 172.25.1.4

this ip-address is my vm-address and I try to connect to proftpd on the same machine.

I'm sure what the problem is comes from my proftpd configuration.
Here is my proftpd.conf:

proftpd.conf

my proftpd / ldap.conf:

ldap.conf

Many Thanks !

mysql – CentOS 6.9 The start of mysqld fails without innodb_force_recovery = 3

Please help me. I googled and searched here, but I could not solve my problem.

The problem is, that Service Mysqld start fails but when I write innodb_force_recovery = 3 Mysqld starts in my.cnf. Also in this case you can use mysql CLI and after changing the database Show tables; answers "lost connection to the server."

My surroundings are
CentOS 6,9 (final)
mysql Ver 14.14 Distrib 5.6.42 for Linux (x86_64) with EditLine wrapper

Here is my.cnf

# To change the settings, see
# http://dev.mysql.com/doc/refman/5.6/en/server-configuration-defaults.html

[mysqld]
#innodb_force_recovery = 3
#
# Remove the leading # and set the amount of RAM for the most important data
# Cache in MySQL. Start with 70% of total dedicated server memory, otherwise 10%.
# innodb_buffer_pool_size = 128M
#
# Remove the leading # to enable a very important data integrity option: Logging
# switches between the backups to the binary log.
# log_bin
#
# Remove the leading # to set options that are especially useful for report servers.
# Server default settings are faster for transactions and fast SELECTs.
# Adjust the size as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir = / var / lib / mysql
socket = / var / lib / mysql / mysql.sock
tmpdir = / tmp /
explicit_defaults_for_timestamp = 1

# Disabling symbolic links is recommended to avoid various security risks
symbolic links = 0

# Recommended in the default setting of MySQL
sql_mode = NO_ENGINE_SUBSTITUTION, STRICT_TRANS_TABLES 

[mysqld_safe]
log-error = / var / log / mysqld.log
pid-file = / var / run / mysqld / mysqld.pid

And here is mysqld.log

// Start mysqld with innodb_force_recovery = 3 in my.cnf.
// And stop mysqld to edit my.cnf.

2018-12-19 22:33:23 31032 [Note] Plugin & # 39; FEDERATED & # 39; is deactivated.
2018-12-19 22:33:23 31032 [Note] InnoDB: Using Atomics to Count Buffer Pool Pages
2018-12-19 22:33:23 31032 [Note] InnoDB: The InnoDB memory heap is disabled
2018-12-19 22:33:23 31032 [Note] InnoDB: Mutexes and rw_locks use GCC Atomic Builds
2018-12-19 22:33:23 31032 [Note] InnoDB: Storage barrier is not used
2018-12-19 22:33:23 31032 [Note] InnoDB: Compressed tables use Zlib 1.2.11
2018-12-19 22:33:23 31032 [Note] InnoDB: Linux native AIO use
2018-12-19 22:33:23 31032 [Note] InnoDB: Use CPU crc32 instructions
2018-12-19 22:33:23 31032 [Note] InnoDB: buffer pool being initialized, size = 128.0M
2018-12-19 22:33:23 31032 [Note] InnoDB: Initialization of the buffer pool completed
2018-12-19 22:33:23 31032 [Note] InnoDB: The highest supported file format is Barracuda.
2018-12-19 22:33:23 31032 [Note] InnoDB: 128 rollback segment (s) are active.
2018-12-19 22:33:23 31032 [Note] InnoDB: 5.6.42 started; Protocol sequence number 4940380617
2018-12-19 22:33:23 31032 [Note] InnoDB: !!! innodb_force_recovery is set to 3 !!!
2018-12-19 22:33:23 31032 [Note] Server host name (binding address): & # 39; * & # 39 ;; Harbor: 3306
2018-12-19 22:33:23 31032 [Note] IPv6 is available.
2018-12-19 22:33:23 31032 [Note]   - & # 39;; & # 39; resolves to & # 39; :: & # 39; on;
2018-12-19 22:33:23 31032 [Note] Server socket created on IP: & # 39; :: & # 39 ;.
2018-12-19 22:33:23 31032 [Note] Event Scheduler: 0 events loaded
2018-12-19 22:33:23 31032 [Note] / usr / sbin / mysqld: ready for connections.
Version: & # 39; 5.6.42 & # 39; Socket: & # 39; /var/lib/mysql/mysql.sock' Port: 3306 MySQL Community Server (GPL)
2018-12-19 22:33:55 31032 [Note] / usr / sbin / mysqld: Normal shutdown

2018-12-19 22:33:55 31032 [Note] 0 Client Threads give the chance to die cruelly
2018-12-19 22:33:55 31032 [Note] Event Scheduler: Delete the queue. 0 events
2018-12-19 22:33:55 31032 [Note] Shut down slave threads
2018-12-19 22:33:55 31032 [Note] 0 remaining clients are forcibly disconnected
2018-12-19 22:33:55 31032 [Note] Binlog-end
2018-12-19 22:33:55 31032 [Note] Shut down the plugin partition
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_SYS_DATAFILES & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_SYS_TABLESPACES & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_SYS_FOREIGN_COLS & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_SYS_FOREIGN & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_SYS_FIELDS & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_SYS_COLUMNS & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_SYS_INDEXES & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_SYS_TABLESTATS & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_SYS_TABLES & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_FT_INDEX_TABLE & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_FT_INDEX_CACHE & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_FT_CONFIG & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_FT_BEING_DELETED & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_FT_DELETED & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_FT_DEFAULT_STOPWORD & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_METRICS & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_BUFFER_POOL_STATS & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_BUFFER_PAGE_LRU & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_BUFFER_PAGE & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_CMP_PER_INDEX_RESET & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_CMP_PER_INDEX & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_CMPMEM_RESET & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_CMPMEM & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_CMP_RESET & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_CMP & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_LOCK_WAITS & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_LOCKS & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; INNODB_TRX & # 39; shut down
2018-12-19 22:33:55 31032 [Note] Plugin & # 39; InnoDB & # 39; shut down
2018-12-19 22:33:55 31032 [Note] InnoDB: FTS optimizes the termination of the thread.
2018-12-19 22:33:55 31032 [Note] InnoDB: shutdown will start ...
2018-12-19 22:33:56 31032 [Note] InnoDB: shutdown completed; Protocol sequence number 4940380617
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; PERFORMANCE_SCHEMA & # 39; shut down
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; BLACKHOLE & # 39; shut down
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; ARCHIVE & # 39; shut down
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; MyISAM & # 39; shut down
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; CSV & # 39; shut down
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; MEMORY & # 39; shut down
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; MRG_MYISAM & # 39; shut down
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; sha256_password & # 39; shut down
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; mysql_old_password & # 39; shut down
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; mysql_native_password & # 39; shut down
2018-12-19 22:33:56 31032 [Note] Plugin & # 39; binlog & # 39; shut down
2018-12-19 22:33:56 31032 [Note] / usr / sbin / mysqld: shutdown complete

// Start mysqld by commenting out innodb_force_recovery = 3 in my.cnf.

2018-12-19 22:35:04 31471 [Note] Plugin & # 39; FEDERATED & # 39; is deactivated.
2018-12-19 22:35:04 31471 [Note] InnoDB: Using Atomics to Count Buffer Pool Pages
2018-12-19 22:35:04 31471 [Note] InnoDB: The InnoDB memory heap is disabled
2018-12-19 22:35:04 31471 [Note] InnoDB: Mutexes and rw_locks use GCC Atomic Builds
2018-12-19 22:35:04 31471 [Note] InnoDB: Storage barrier is not used
2018-12-19 22:35:04 31471 [Note] InnoDB: Compressed tables use Zlib 1.2.11
2018-12-19 22:35:04 31471 [Note] InnoDB: Linux native AIO use
2018-12-19 22:35:04 31471 [Note] InnoDB: Use CPU crc32 instructions
2018-12-19 22:35:04 31471 [Note] InnoDB: buffer pool being initialized, size = 128.0M
2018-12-19 22:35:04 31471 [Note] InnoDB: Initialization of the buffer pool completed
2018-12-19 22:35:04 31471 [Note] InnoDB: The highest supported file format is Barracuda.
2018-12-19 22:35:04 31471 [Note] InnoDB: 128 rollback segment (s) are active.
2018-12-19 22:35:04 31471 [Note] InnoDB: Waiting for the start of the cleanup
InnoDB: Error: The table space ID is 94 in the data dictionary
InnoDB: but in the file ./mysql/innodb_table_stats.ibd it is 1!
2018-12-19 22:35:04 7fd0d6bfd700 InnoDB: assertion error in thread 140534932821760 in file fil0fil.cc line 797
InnoDB: We purposely create a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: Even if you receive repeated assertion errors or crashes
InnoDB: It can be right after the start of mysqld
InnoDB: Corruption of the InnoDB table space. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: About Forcing Recovery.
13:35:04 UTC - mysqld received signal 6;
This may be because you have found an error. It is also possible that this is binary
or one of the libraries it was linked to is damaged, improperly built,
or configured incorrectly. This error can also be caused by faulty hardware.
We will do our best to gather information that will hopefully help
diagnose the problem but since we already crashed,
Something is definitely wrong and that can fail.

key_buffer_size = 8388608
read_buffer_size = 131072
max_used_connections = 0
max_threads = 151
thread_count = 0
Connection number = 0
It is possible that mysqld can use up to
key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads = 68108 kBytes in memory
Hope that's ok; If not, reduce some variables in the equation.

Thread pointer: 0x0
Try backtrace. You can use the following information to find out
where mysqld died If you do not see any news after that, something went wrong
terribly wrong ...
stack_bottom = 0 thread_stack 0x40000
/ usr / sbin / mysqld (my_print_stacktrace + 0x35)[0x8e7635]
/ usr / sbin / mysqld (handle_fatal_signal + 0x494)[0x669414]
/lib64/libpthread.so.0(+0xf7e0)[0x7fd1089077e0]
/lib64/libc.so.6(gsignal+0x35)[0x7fd1073a74f5]
/lib64/libc.so.6(abort+0x175)[0x7fd1073a8cd5]
/ usr / sbin / mysqld[0xa9dc66]
/ usr / sbin / mysqld[0xa9dcc5]
/ usr / sbin / mysqld[0xa9e0a6]
/ usr / sbin / mysqld[0xa6c7bd]
/ usr / sbin / mysqld[0xa6cf2b]
/ usr / sbin / mysqld[0xa5aee1]
/ usr / sbin / mysqld[0xa4655a]
/ usr / sbin / mysqld[0x9e7848]
/ usr / sbin / mysqld[0x9e4f5d]
/ usr / sbin / mysqld[0x9e510c]
/ usr / sbin / mysqld[0x9e7041]
/ usr / sbin / mysqld[0x9b5305]
/ usr / sbin / mysqld[0xa1056b]
/ usr / sbin / mysqld[0xa014e7]
/lib64/libpthread.so.0(+0x7aa1)[0x7fd1088ffaa1]
/lib64/libc.so.6(clone+0x6d)[0x7fd10745dc4d]
See the man page at http://dev.mysql.com/doc/mysql/en/crashing.html
Information to help you find out what is causing the crash.

Please help me.

Polynomials – Basic 3D interpolation fails

I have seen a few other posts that asked for the "unstructured grid" error interpolation, Here's a minimal (not working) example of the problem:

z = RandomReal[{-1, 1}, 50];
xy = RandomPoint[Rectangle[{0, 0}, {1, 1}], 50];
interpolation[Thread[{xy, z}]InterpolationOrder -> 2]

Enter the image description here

One way to work around this is to use InterpolatingPolynomial like this:

data = thread[{xy, z}];
ip = InterpolatingPolynomial[data, {x, y}];
show[Plot3D[ip, {x, 0, 1}, {y, 0, 1}],
Graphics3D[Point[Flatten /@ data]]]

Enter the image description here

In practice, however, it does not work well because the polynomial orders are uncontrollable (too high):

Enter the image description here

Are there any possible alternatives to succeed quadratically? InterpolationOrder in the interpolation?

The MinGw make.exe link fails when using PowerShell

I have a gcc project that uses build makefile. When I create the project from PowerShell, the linker fails and I get the following message:

/ bin / sh: /path-to-makefile-folder/C:/MinGW/msys/1.0/bin/make.exe: no
such file or directory make.exe ": *** [_build/project.out] Error 127

The process runs correctly using a command prompt.
Any ideas?

System is Windows 10, PSVersion 5.1.17763.134

Error – Bitcoin Core 0.17 fails after loading too many purses

I can start the Bitcoin core store with 200 wallets. But if I increase it to 300 purses, it fails. Below is the debug.log when I tried loading 300 wallets.

2018-12-17T01: 36: 27Z Init Message: Wallet is loading ...
2018-12-17T01: 36: 27Z [wallet-201.dat] nFileVersion = 170001
2018-12-17T01: 36: 27Z [wallet-201.dat] Key: 3 plaintext, 0 encrypted, 3 with metadata, 3 in total. Records of unknown wallets: 1
2018-12-17T01: 36: 27Z [wallet-201.dat] Loading the wallet completed in 1 ms
2018-12-17T01: 36: 27Z [wallet-201.dat] setKeyPool.size () = 2
2018-12-17T01: 36: 27Z [wallet-201.dat] mapWallet.size () = 0
2018-12-17T01: 36: 27Z [wallet-201.dat] mapAddressBook.size () = 0
2018-12-17T01: 36: 27Z Init Message: Wallet is loading ...
2018-12-17T01: 36: 27Z [wallet-202.dat] nFileVersion = 170001
2018-12-17T01: 36: 27Z [wallet-202.dat] Key: 3 plaintext, 0 encrypted, 3 with metadata, 3 in total. Records of unknown wallets: 1
2018-12-17T01: 36: 39Z [wallet-202.dat] Loading the wallet in 12012ms completed
2018-12-17T01: 36: 39Z Init Message: Rescan ...
2018-12-17T01: 36: 39Z [wallet-202.dat] Last scan of 1447907 blocks (from block 0) ...
2018-12-17T01: 36: 39Z [wallet-202.dat] Rescan started from block 1447885 ...
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 14930383)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 14955195)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15731604)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15152698)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 14994412)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15000180)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15237899)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15073409)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15076691)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15162221)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15175705)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15238839)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15734430)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15746232)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15755504)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15759768)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15780715)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15795130)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15814178)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15841983)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15844548)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15870120)
2018-12-17T01: 36: 39Z File /root/.bitcoin/testnet3/blocks/blk00155.dat can not be opened
2018-12-17T01: 36: 39Z ERROR: ReadBlockFromDisk: OpenBlockFile for CBlockDiskPos failed (nFile = 155, nPos = 15897975)
2018-12-17T01: 36: 39Z [wallet-202.dat] Rescan to 1 ms
2018-12-17T01: 36: 39Z [wallet-202.dat] setKeyPool.size () = 2
2018-12-17T01: 36: 39Z [wallet-202.dat] mapWallet.size () = 0
2018-12-17T01: 36: 39Z [wallet-202.dat] mapAddressBook.size () = 0
2018-12-17T01: 36: 39Z-Init message: Wallet is loading ...
2018-12-17T01: 36: 51Z [wallet-203.dat] Release wallet
2018-12-17T01: 36: 51Z BerkeleyEnvironment :: Flush: Flush (false)
2018-12-17T01: 36: 51Z BerkeleyEnvironment :: Flush: Flush (false) lasted 0 ms
2018-12-17T01: 36: 51Z

*************************
EXCEPTION: St13runtime_error
BerkeleyBatch: Error 24, database wallet.dat can not be opened
Bitcoin in AppInit ()          

Updates – The 1809 update still fails (after December 14, 2018)

I got a test mashine that I keep updating since the release of W10, but now there seems to be a problem with 1809.

symptoms:

1) Windows 10 "Check for updates" only returns updates for 1803, if available, but informs that MS is distributing the new update …

2) Windows 10 "Update Wizard" offers 1809. He does the job with reboots (even more than one) and only runs one window after completing the process. However, there is no change to the system that persists in 1803. No errors, no notifications, no pops, not even a bug in the event viewer … at least I can fix a bug in the update.

Already done:

1) Troubleshooting – Windows Update: This program is constantly looking for pending updates, but the fix does nothing

2) Complete "Disk Cleanup" performed with elevated privileges …

3) Has performed updating the update folder (stopping update-related services, performing cleaning, restarting services, and rebooting). Even after all that, I'm back at point 1 troubleshooting.

Since this is a test machine, I do not have to install it really clean. I want to see how it refreshes first.

Any ideas that I can try?

Thank you for all the help I have seen too often in the last few weeks.

apt – 16.04.5> 18.04.1 – Update always fails

I have a Xen-based server running Ubuntu 16.04.5 (originally updated from a 14.04 template). Any attempt to upgrade from 16.04.5> 18.04.1 will generate the following error at the end of the upgrade process. I know that the template here is the problem, not the host system that runs Xen. I have another template running on 12.04 that upgrades to 14.04> 16.04 and then finally calls to 18.04.1 without any problems:

Systemd-shim (9-1bzr4ubuntu1) is removed ...
Removed from /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service in /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd from systemd-remote Shim & # 39;
dpkg-divert: Error: When renaming "/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service" is overwritten with
other file & # 39; /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd&#39 ;, not allowed
dpkg: Error Handling Package systemd-shim (--remove):
The script installed after the script was removed returned an exit status for error 2

Does anyone know what the problem might be and how can I end up with a correct, flawless upgrade?

Many Thanks.

Kolla OpenStack deployment fails with "haproxy: waiting for virtual IP address"

I am trying to deploy OpenStack Queens with kolla-ansible (7.0.0) on Ubuntu hosts, following the official instructions.

After successful Bootstrap server and precheck the provide Command fails:

RUNNING TRADER [haproxy : Waiting for virtual IP to appear] ************************************************** ** ********
fatal: [testcloudcontrol01]: FAILED! => {"changed": wrong, "expired": 300, "msg": "Waiting timeout on 10.52.41.98:3306"}
fatal: [testcloudcontrol02]: FAILED! => {"changed": wrong, "expired": 300, "msg": "Waiting timeout on 10.52.41.98:3306"}

The reason for the test is that the test fails kolla_internal_vip_address does not come up

globals.yml

config_strategy: "COPY_ALWAYS"
kolla_base_distro: "ubuntu"
kolla_install_type: "binary"
openstack_release: "queens"
kolla_internal_vip_address: "10.52.41.98"
kolla_internal_fqdn: "testcloudapi.example.com"
kolla_external_vip_address: "{{kolla_internal_vip_address}}"
kolla_external_fqdn: "{{kolla_internal_fqdn}}"
Network interface: "ens160"
api_interface: "ens160"
storage_interface: "ens161"
keepalived_virtual_router_id: "148"

I am currently fixated on queens because I want to replicate our production environment for testing.

The issue of IP Address on one of the nodes where Haproxy is to be deployed:

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group preset qlen 1
link / loopback 00: 00: 00: 00: 00: 00 brd 00: 00: 00: 00: 00: 00
inet 127.0.0.1/8 scope lo lo
valid_lft forever Preferred_lft forever
inet6 :: 1/128 Scope Host
valid_lft forever Preferred_lft forever
2: ens160:  mtu 1500 qdisc mq status UP group preset qlen 1000
link / ether 00: 50: 56: a1: 6a: 2c brd ff: ff: ff: ff: ff: ff
inet 10.52.41.100/24 ​​brd 10.52.41.255 Scope global ens160
valid_lft forever Preferred_lft forever
inet6 fe80 :: 250: 56ff: fea1: 6a2c / 64 area connection
valid_lft forever Preferred_lft forever
3: ens161:  mtu 1500 qdisc mq status UP group preset qlen 1000
link / ether 00: 50: 56: a1: 7d: 07 brd ff: ff: ff: ff: ff: ff
inet 10.52.42.100/24 ​​brd 10.52.42.255 Scope global ens161
valid_lft forever Preferred_lft forever
inet6 fe80 :: 250: 56ff: fea1: 7d07 / 64 Area link
valid_lft forever Preferred_lft forever
4: ens224:  mtu 1500 qdisc mq status UP group preset qlen 1000
link / ether 00: 50: 56: a1: 23: 6d brd ff: ff: ff: ff: ff: ff
inet 10.52.40.100/24 ​​brd 10.52.40.255 Scope global ens224
valid_lft forever Preferred_lft forever
inet6 fe80 :: 250: 56ff: fea1: 236e / 64 Area Connection
valid_lft forever Preferred_lft forever
5: ens256:  mtu 1500 qdisc mq status UP group preset qlen 1000
link / ether 00: 50: 56: a1: 20: 12 brd ff: ff: ff: ff: ff: ff
inet 10.52.44.100/24 ​​brd 10.52.44.255 Scope global ens256
valid_lft forever Preferred_lft forever
inet6 fe80 :: 250: 56ff: fea1: 2012/64 link to the section
valid_lft forever Preferred_lft forever
6: docker0:  mtu 1500 qdisc noqueue state DOWN group preset
link / ether 02: 42: b0: 8a: 93: e7 brd ff: ff: ff: ff: ff: ff
Inet 172.17.0.1/16 Scope of Global Docker0
valid_lft forever Preferred_lft forever

The nodes are VMware virtual machines with VMXNet3 network.

Issue of Docker logs are preserved:

+ sudo -E kolla_set_configs
INFO: __ main __: Loading the configuration file under /var/lib/kolla/config_files/config.json
INFO: __ main __: Checks the configuration file
INFO: __ main __: The Kolla configuration strategy is set to COPY_ALWAYS
INFO: __ main __: Copy service configuration files
INFO: __ main __: Delete /etc/keepalived/keepalived.conf
INFO: __ main __: Copy from /var/lib/kolla/config_files/keepalived.conf to /etc/keepalived/keepalived.conf
INFO: __ main __: Set the permission for /etc/keepalived/keepalived.conf
INFO: __ main __: command to execute
++ cat / run_command
+ CMD = & # 39; / usr / sbin / keepalived -nld -p /run/keepalived.pid'
+ ARGS =
+ [[ ! -n '' ]]+. kolla_extend_start
++ modprobe ip_vs
++ & # 39;[' -f /run/keepalived.pid ']& # 39;
+ echo & # 39; command executed: & # 39;  & # 39; & # 39; / usr / sbin / keepalived -nld -p /run/keepalived.pid & # 39;  & # 39; & # 39; & # 39;
Running command: & # 39; / usr / sbin / keepalived -nld -p /run/keepalived.pid'
+ exec / usr / sbin / keepalived -nld -p / run / keepalived.pid
Thu Dec 13 12:10:26 2018: Starting Keepalived Version 1.3.9 (10 / 21,2017)
Thu Dec 13 12:10:26 2018: Opening file & # 39; /etc/keepalived/keepalived.conf&#39 ;.
Thu Dec 13 12:10:26 2018: Start of the Healthcheck children's process, pid = 11
Thu Dec 13 12:10:26 2018: Opening file & # 39; /etc/keepalived/keepalived.conf&#39 ;.
Thu Dec 13 12:10:26 2018: VRRP sub-process is started, pid = 12
Thu Dec 13 12:10:26 2018: ------< Global definitions >------
Thu Dec 13 12:10:26 2018: Router ID = testcloudcontrol01.example.com
Thu Dec 13 12:10:26 2018: standard interface = eth0
Thu Dec 13 12:10:26 2018: LVS flush = wrong
Thu Dec 13 12:10:26 2018: VRRP IPv4 Mcast Group = 224.0.0.18
Thu Dec 13 12:10:26 2018: VRRP IPv6 Mcast Group = ff02 :: 12
Thu Dec 13 12:10:26 2018: Indispensable ARP delay = 5
Thu Dec 13 12:10:26 2018: Free ARP repetition = 5
Thu Dec 13 12:10:26 2018: Indispensable ARP update timer = 0
Thu Dec 13 12:10:26 2018: Repeat ARP update retry = 1
Thu Dec 13 12:10:26 2018: Indispensable lower priority ARP delay = 4294
Thu Dec 13 12:10:26 2018: Indispensable ARP repetition with lower priority = -1
Thu Dec 13 12:10:26 2018: Submit the ad after receiving a lower priority
Thu 13.12. 12:10:26 2018: Submit an ad after the higher priority = false
Thu Dec 13 12:10:26 2018: Free ARP interval = 0
Thu Dec 13 12:10:26 2018: Unnecessary NA interval = 0
Thu Dec 13 12:10:26 2018: VRRP standard protocol version = 2
Thu Dec 13 12:10:26 2018: Iptables input string = INPUT
Thu Dec 13 12:10:26 2018: With ipsets = true
Thu Dec 13 12:10:26 2018: ipset IPv4 address set = Keepalived
Thu Dec 13 12:10:26 2018: ipset IPv6 address set = keepalived6
Thu Dec 13 12:10:26 2018: ipset IPv6 address, iface set = keepalived_if6
Thu Dec 13 12:10:26 2018: VRRP check unicast_src = false
Thu Dec 13 12:10:26 2018: VRRP Skip the adresses = wrong
Thu Dec 13 12:10:26 2018: VRRP strict mode = wrong
Thu Dec 13 12:10:26 2018: VRRP process priority = 0
Thu Dec 13 12:10:26 2018: VRRP do not swap = wrong
Thu Dec 13 12:10:26 2018: Checker process priority = 0
Thu Dec 13 12:10:26 2018: Checker do not exchange = wrong
Thu Dec 13 12:10:26 2018: SNMP has been deactivated
Thu Dec 13 12:10:26 2018: SNMP Checker disabled
Thu Dec 13 12:10:26 2018: SNMP RFCv2 disabled
Thu Dec 13 12:10:26 2018: SNMP RFCv3 disabled
Thu Dec 13 12:10:26 2018: SNMP traps disabled
Thu Dec 13 12:10:26 2018: SNMP-Socket = Default (Unix: / var / agentx / master)
Thu Dec 13 12:10:26 2018: Network namespace = (default)
Thu Dec 13 12:10:26 2018: DBus disabled
Thu Dec 13 12:10:26 2018: DBus service name = (null)
Thu Dec 13 12:10:26 2018: Script security disabled
Thu Dec 13 12:10:26 2018: Default script uid: gid 0: 0
Thu Dec 13 12:10:26 2018: Register the kernel-netlink-reflector
Thu Dec 13 12:10:26 2018: Register the kernel netlink command channel
Thu Dec 13 12:10:26 2018: Register a free ARP channel
Thu Dec 13 12:10:26 2018: Opening file & # 39; /etc/keepalived/keepalived.conf&#39 ;.
Thu Dec 13 12:10:26 2018: WARNING - The default user & # 39; keepalived_script & # 39; for the script execution does not exist. Please create.
Thu Dec 13 12:10:26 2018: Auth_pass is truncated to 8 characters
Thu Dec 13 12:10:26 2018: SECURITY INFRINGEMENT - Scripts are running, but script_security is not enabled.
Thu Dec 13 12:10:26 2018: ------< Global definitions >------
Thu Dec 13 12:10:26 2018: Router ID = testcloudcontrol01.example.com
Thu Dec 13 12:10:26 2018: standard interface = eth0
Thu Dec 13 12:10:26 2018: LVS flush = wrong
Thu Dec 13 12:10:26 2018: VRRP IPv4 Mcast Group = 224.0.0.18
Thu Dec 13 12:10:26 2018: VRRP IPv6 Mcast Group = ff02 :: 12
Thu Dec 13 12:10:26 2018: Indispensable ARP delay = 5
Thu Dec 13 12:10:26 2018: Free ARP repetition = 5
Thu Dec 13 12:10:26 2018: Indispensable ARP update timer = 0
Thu Dec 13 12:10:26 2018: Repeat ARP update retry = 1
Thu Dec 13 12:10:26 2018: Indispensable lower priority ARP delay = 5
Thu Dec 13 12:10:26 2018: Repeat lower priority ARP = 5
Thu Dec 13 12:10:26 2018: Submit the ad after receiving a lower priority
Thu 13.12. 12:10:26 2018: Submit an ad after the higher priority = false
Thu Dec 13 12:10:26 2018: Free ARP interval = 0
Thu Dec 13 12:10:26 2018: Unnecessary NA interval = 0
Thu Dec 13 12:10:26 2018: VRRP standard protocol version = 2
Thu Dec 13 12:10:26 2018: Iptables input string = INPUT
Thu Dec 13 12:10:26 2018: With ipsets = false
Thu Dec 13 12:10:26 2018: ipset IPv4 address set = Keepalived
Thu Dec 13 12:10:26 2018: ipset IPv6 address set = keepalived6
Thu Dec 13 12:10:26 2018: ipset IPv6 address, iface set = keepalived_if6
Thu Dec 13 12:10:26 2018: VRRP check unicast_src = false
Thu Dec 13 12:10:26 2018: VRRP Skip the adresses = wrong
Thu Dec 13 12:10:26 2018: VRRP strict mode = wrong
Thu Dec 13 12:10:26 2018: VRRP process priority = 0
Thu Dec 13 12:10:26 2018: VRRP do not swap = wrong
Thu Dec 13 12:10:26 2018: Checker process priority = 0
Thu Dec 13 12:10:26 2018: Checker do not exchange = wrong
Thu Dec 13 12:10:26 2018: SNMP has been deactivated
Thu Dec 13 12:10:26 2018: SNMP Checker disabled
Thu Dec 13 12:10:26 2018: SNMP RFCv2 disabled
Thu Dec 13 12:10:26 2018: SNMP RFCv3 disabled
Thu Dec 13 12:10:26 2018: SNMP traps disabled
Thu Dec 13 12:10:26 2018: SNMP-Socket = Default (Unix: / var / agentx / master)
Thu Dec 13 12:10:26 2018: Network namespace = (default)
Thu Dec 13 12:10:26 2018: DBus disabled
Thu Dec 13 12:10:26 2018: DBus service name = (null)
Thu Dec 13 12:10:26 2018: Script security disabled
Thu Dec 13 12:10:26 2018: Default script uid: gid 0: 0
Thu Dec 13 12:10:26 2018: ------< VRRP Topology >------
Thu Dec 13 12:10:26 2018: VRRP instance = kolla_internal_vip_148
Thu Dec 13 12:10:26 2018: Using VRRPv2
Thu Dec 13 12:10:26 2018: Want State = BACKUP
Thu Dec 13 12:10:26 2018: Runs on device = ens160
Thu Dec 13 12:10:26 2018: Skip the display of IP addresses = no
Thu Dec 13 12:10:26 2018: Enforce strict VRRP compliance = no
Thu Dec 13 12:10:26 2018: Using src_ip = 10.52.41.100
Thu Dec 13 12:10:26 2018: Indispensable ARP delay = 5
Thu Dec 13 12:10:26 2018: Free ARP repetition = 5
Thu Dec 13 12:10:26 2018: Indispensable ARP update timer = 0
Thu Dec 13 12:10:26 2018: Repeat ARP update retry = 1
Thu Dec 13 12:10:26 2018: Indispensable lower priority ARP delay = 5
Thu Dec 13 12:10:26 2018: Repeat lower priority ARP = 5
Thu Dec 13 12:10:26 2018: Submit the ad after receiving a lower priority
Thu 13.12. 12:10:26 2018: Submit an ad after the higher priority = false
Thu Dec 13 12:10:26 2018: Virtual Router ID = 148
Thu Dec 13 12:10:26 2018: Priority = 1
Thu Dec 13 12:10:26 2018: Display interval = 1 sec
Thu Dec 13 12:10:26 2018: Accept activated
Thu Dec 13 12:10:26 2018: Disability disabled
Thu Dec 13 12:10:26 2018: Promotion_Secondary disabled
Thu Dec 13 12:10:26 2018: Authentication type = SIMPLE_PASSWORD
Thu Dec 13 12:10:26 2018: Password = 0RXbQYFF
Thu Dec 13 12:10:26 2018: Tracked scripts = 1
Thu Dec 13 12:10:26 2018: check_alive weight 0
Thu Dec 13 12:10:26 2018: Virtual IP = 1
Thu Dec 13 12:10:26 2018: 10.52.41.98/32 dev ens160 Scope global
Thu Dec 13 12:10:26 2018: ------< VRRP Scripts >------
Thu Dec 13 12:10:26 2018: VRRP script = check_alive
Thu Dec 13 12:10:26 2018: Command = /check_alive.sh
Thu Dec 13 12:10:26 2018: Interval = 2 sec
Thu Dec 13 12:10:26 2018: Timeout = 0 sec
Thu Dec 13 12:10:26 2018: Weight = 0
Thu Dec 13 12:10:26 2018: Ascent = 10
Thu Dec 13 12:10:26 2018: Case = 2
Thu Dec 13 12:10:26 2018: Uncertain = No
Thu Dec 13 12:10:26 2018: Status = INIT
Thu Dec 13 12:10:26 2018: Script uid: gid = 0: 0
Thu Dec 13 12:10:26 2018: ------< NIC >------
Thu Dec 13 12:10:26 2018: Name = see
Thu Dec 13 12:10:26 2018: Index = 1
Thu Dec 13 12:10:26 2018: IPv4 address = 127.0.0.1
Thu Dec 13 12:10:26 2018: IPv6 address = ::
Thu Dec 13 12:10:26 2018: is UP
Thu Dec 13 12:10:26 2018: RUNNING
Thu Dec 13 12:10:26 2018: MTU = 65536
Thu Dec 13 12:10:26 2018: HW-Type = LOOPBACK
Thu Dec 13 12:10:26 2018: ------< NIC >------
Thu Dec 13 12:10:26 2018: Name = ens160
Thu Dec 13 12:10:26 2018: Index = 2
Thu Dec 13 12:10:26 2018: IPv4 address = 10.52.41.100
Thu Dec 13 12:10:26 2018: IPv6 address = fe80 :: 250: 56ff: fea1: 6a2c
Thu Dec 13 12:10:26 2018: MAC = 00: 50: 56: a1: 6a: 2c
Thu Dec 13 12:10:26 2018: is UP
Thu Dec 13 12:10:26 2018: RUNNING
Thu Dec 13 12:10:26 2018: MTU = 1500
Thu Dec 13 12:10:26 2018: HW type = ETHERNET
Thu Dec 13 12:10:26 2018: ------< NIC >------
Thu Dec 13 12:10:26 2018: Name = ens161
Thu Dec 13 12:10:26 2018: Index = 3
Thu Dec 13 12:10:26 2018: IPv4 address = 10.52.42.100
Thu Dec 13 12:10:26 2018: IPv6 address = fe80 :: 250: 56ff: fea1: 7d07
Thu Dec 13 12:10:26 2018: MAC = 00: 50: 56: a1: 7d: 07
Thu Dec 13 12:10:26 2018: is UP
Thu Dec 13 12:10:26 2018: RUNNING
Thu Dec 13 12:10:26 2018: MTU = 1500
Thu Dec 13 12:10:26 2018: HW type = ETHERNET
Thu Dec 13 12:10:26 2018: ------< NIC >------
Thu Dec 13 12:10:26 2018: Name = ens224
Thu Dec 13 12:10:26 2018: Index = 4
Thu Dec 13 12:10:26 2018: IPv4 address = 10.52.40.100
Thu Dec 13 12:10:26 2018: IPv6 address = fe80 :: 250: 56ff: fea1: 236e
Thu Dec 13 12:10:26 2018: MAC = 00: 50: 56: a1: 23: 6e
Thu Dec 13 12:10:26 2018: is UP
Thu Dec 13 12:10:26 2018: RUNNING
Thu Dec 13 12:10:26 2018: MTU = 1500
Thu Dec 13 12:10:26 2018: HW type = ETHERNET
Thu Dec 13 12:10:26 2018: ------< NIC >------
Thu Dec 13 12:10:26 2018: Name = ens256
Thu Dec 13 12:10:26 2018: Index = 5
Thu Dec 13 12:10:26 2018: IPv4 address = 10.52.44.100
Thu Dec 13 12:10:26 2018: IPv6 address = fe80 :: 250: 56ff: fea1: 2012
Thu Dec 13 12:10:26 2018: MAC = 00: 50: 56: a1: 20: 12
Thu Dec 13 12:10:26 2018: is UP
Thu Dec 13 12:10:26 2018: RUNNING
Thu Dec 13 12:10:26 2018: MTU = 1500
Thu Dec 13 12:10:26 2018: HW type = ETHERNET
Thu Dec 13 12:10:26 2018: ------< NIC >------
Thu Dec 13 12:10:26 2018: Name = Docker0
Thu Dec 13 12:10:26 2018: Index = 6
Thu Dec 13 12:10:26 2018: IPv4 address = 172.17.0.1
Thu Dec 13 12:10:26 2018: IPv6 address = ::
Thu Dec 13 12:10:26 2018: MAC = 02: 42: B0: 8a: 93: e7
Thu Dec 13 12:10:26 2018: is UP
Thu Dec 13 12:10:26 2018: MTU = 1500
Thu Dec 13 12:10:26 2018: HW type = ETHERNET
Thu Dec 13 12:10:26 2018: Using the LinkWatch Kernel Netlink Reflector ...
Thu Dec 13 12:10:26 2018: VRRP_Instance (kolla_internal_vip_148) Enter BACKUP STATUS
Thu Dec 13 12:10:26 2018: /check_alive.sh ended with status 1
Thu Dec 13 12:10:28 2018: /check_alive.sh ended with status 1
Thu Dec 13 12:10:30 2018: VRRP_Instance (kolla_internal_vip_148) Now in error state
Thu Dec 13 12:10:30 2018: /check_alive.sh ended with status 1
Thu Dec 13 12:10:32 2018: /check_alive.sh ended with status 1
[message repeats until I stop the container]

That's it, the two keepalived instances remain in FAULT status, the IP address is not enabled on any of the VMs.

I have read this question and the answer, although I have no error messages in the log files:

  • keepalived_virtual_router_id has been changed and is unique
  • I ran kolla-genpwd once again. I confirmed that keepalived_password is employed /etc/kolla/passwords.yml
  • kolla_internal_vip_address is reachable from Network Interface, The main IP of this interface is on the same network. I can manually set the additional IP address and it works.
  • kolla-ansible prechecks passes
  • Selinux is not active on Ubuntu

On the hypervisor page, I tried activating Promiscuous mode for the port group of this interface. That did not make a difference.

Using Microsoft.Sharepoint.Client ListItem.Update fails when attempting to perform batch updates

I've written a component that updates a SharePoint 2010 list using the Sharepoint client in C #. This works fine if I make it line by line and call ListItem.Update () followed by Context.ExecuteQuery () for each line.

Unfortunately, the performance for a large list is very slow and takes more than 2 hours to update about 3000 lines. We're investigating why this might be possible (suggestions are welcome!), As other similar size lists can be run smoothly, but I also try to stack the updates by calling the listItem Update () method on each line ExecuteQuery, however, only once every 100 rows.

However, when I try to do that, I find that the ExecuteQuery () call fails with a SharePoint error The remote server returned an error: (400) Bad request.

Can someone see where the mistake could be or give advice? Below you will find the relevant parts of the code. I've cut out some of the details, as this all works well if I update and run it for each line, so I know there's no problem there.

ClientContext spClientContext = new ClientContext (mySharepointSite);
spClientContext.Credentials = new System.Net.NetworkCredential (mySharepointUser, mySharepointPwd, mySharepointDomain);

// There are two copies of the list - one for reading and one for updates
Microsoft.SharePoint.Client.List updateList = updateContext.Web.Lists.GetByTitle (mySharepointList);
Microsoft.SharePoint.Client.List myList = spClientContext.Web.Lists.GetByTitle (mySharepointList);

CamlQuery q = new CamlQuery ();
q.ViewXml =
@ "
    
        
            
        
    
";

ListItemCollection spRows = myList.GetItems (q);
spClientContext.Load (spRows);
spClientContext.ExecuteQuery ();

foreach (ListItem row in rows)
{
int id = (int) spRow["ID"];
ListItem updateRow = updateList.GetItemById ((int) id);
// Processing was truncated to find out changes and find a new value
updateRow[myCaption] = newVal;
updateRow.Update ();
updateCount ++;
if (updateCount% 100 == 0)
{
updateContext.ExecuteQuery ();
}
}