(Source)

A few steps:

sudo apt-get install software-properties-common dirmngr
wget -qO - https://mariadb.org/mariadb_release_signing_key.asc | sudo apt-key add -
nano /etc/apt/sources.list.d/mariadb.list

In mariadb.list we add the two below lines:

deb [arch=amd64,i386,ppc64el] http://mirror.23media.de/mariadb/repo/10.4/debian stretch main
deb-src http://mirror.23media.de/mariadb/repo/10.4/debian stretch main

Then:

apt-get update
apt-get install mariadb-server

For me the issue was this part of the XML request: <AddWebPart xmlns='http://microsoft.com/sharepoint/webpartpages/'> (with a / at the end of the url) instead of <AddWebPart xmlns='http://microsoft.com/sharepoint/webpartpages'>.

Sometimes, when I open a new tab in Chrome, it first tries to get chrome-search://local-ntp/local-ntp.html and while it’s doing it, I cannot enter any URL. Eventually it will popup a message asking me if I want to wait or exit the page…

The way I found to fix it is to go to the page chrome://flags/#use-google-local-ntp, then I disabled “Enable using the Google local NTP”

Gmail could report back this error message: “Our system has detected an unusual rate of unsolicited mail originating from your IP address”

If your DKIM, SPF and DMARC are all set and your emails are correctly identified, then you may want to check the both links:

• Good links to get help on what to do: https://support.google.com/mail/thread/9191597?hl=en
• The form to be removed from GMail blacklist: https://support.google.com/mail/contact/bulk_send_new

Due to the 5,000 items threshold limitation it can become very frustrating to administrate Sharepoint. For example, if your list has more than 5,000 items, you cannot add an index, delete a lookup/people column, delete the list or the website, and more !

Hopefully some of the operations can be done with REST API, and in my organization the threshold limitation is removed during the night (1am to 4am). By combining a schedule service (like node-schedule) with my library SharepointPlus I can run this admin tasks during the night while my virtual computer is running.

To delete a column

$SP().ajax({
  url:"https://company.com/sharepoint/team/sales/_api/web/lists/getbytitle('My List')/fields/getbytitle('Column To Delete')",
  method: "POST",
  headers: {
    "IF-MATCH": "*",
    "X-HTTP-Method": "DELETE"
  }
});

To index a column

$SP().ajax({
  url:"https://company.com/sharepoint/team/sales/_api/web/lists/getbytitle('My List')/fields/getbytitle('Column to Index')",
  method: "POST",
  body:JSON.stringify({
    "__metadata":{ type: "SP.Field" },
    "Indexed":true
  }),
  headers: {
    "IF-MATCH": "*",
    "X-HTTP-Method": "MERGE"
  }
})

To delete a list

$SP().ajax({
  url:"https://company.com/sharepoint/team/sales/_api/web/lists/getbytitle('List To Delete')",
  method: "POST",
  headers: {
    "IF-MATCH": "*",
    "X-HTTP-Method": "DELETE"
  }
})

To delete a list

$SP().ajax({
  url:"https://company.com/sharepoint/team/sales/_api/web/lists/getbytitle('List To Delete')",
  method: "POST",
  headers: {
    "IF-MATCH": "*",
    "X-HTTP-Method": "DELETE"
  }
})

To delete a site

$SP().ajax({
  url:"https://company.com/sharepoint/team/sales/website_to_delete/_api/web/",
  method: "POST",
  headers: {
    "X-HTTP-Method": "DELETE"
  }
})

Finding the documentation for the Search REST API of Sharepoint is difficult…. There is a very old blog post that I’m going to replicate here to give more visibility:

Location of the Search Rest service

The Search REST service is located at the following URI: http://host/site/_api/search

The Search REST API

The Search REST service exposed by the URI specified above provides the following methods or entry points:

Query Parameters

The following table lists the query parameters available for the query entry point:

Suggest Parameters

The following table lists the query parameters available from the suggest entry point:

 References:

• [MS-SRCHCSOM]: Search Client Query Protocol Specification
• Search in SharePoint 2013 on MSDN

Examples

A postquery request will look like:

POST http://localhost/_api/search/postquery HTTP/1.1
Accept: application/json;odata=verbose
Content-Type: application/json;odata=verbose
Host: localhost
Content-Length: 419

{

 'request': {
     'Querytext': 'sharepoint',
     'StartRow':1,
     'RowLimit':8,
     'SelectProperties': {
          'results': ['Title','ContentSource','DisplayAuthor']
     },
     'TrimDuplicates':true,
     'Refiners':'companies,contentclass,ContentType(filter=7/0/*),FileExtension(filter=7/0/*),FileType(filter=6/0/*)',
     'RefinementFilters': {'results': ['filetype:equals("pptx")'] }
  }
}

After diging around for an exim4 problem (remote_smtp: message is too big (transport limit = 1)), I found the answer in this post:

Add “IGNORE_SMTP_LINE_LENGTH_LIMIT=1” in the exim4 config file (/etc/exim4/update-exim4.conf.conf), then restart exim4

With Sharepoint you can use SP.Utilities.Utility.SendEmail to send email in JavaScript, however you could receive the below error:

“The e-mail message cannot be sent. Make sure the e-mail has a valid recipient.”

After searching the web, I found the solution: instead of using an email address for the recipients you have to use the userDomain with “i:0#.w|”.

For example, if the user is John Doe, and his email is john_doe@company.com, then you should use something like i:0#.w|domain\\john_doe.

When I want to reload my MariaDB server, I receive the below error:

/usr/bin/mysqladmin: connect to server at ‘localhost’ failed
error: ‘Access denied for user ‘root’@’localhost’ (using password: NO)’

The solution is to provide the root’s password in the file `/etc/mysql/debian.cnf` and then the error is gone!

Il faut régulièrement penser à mettre à jour son serveur Kimsufi.

Je vais essayer d’expliquer brièvement les étapes à suivre pour cela.

1. On va d’abord sauvegarder les données :

   mkdir /root/svg_special; cp -R /var/lib/dpkg /root/svg_special/; cp /var/lib/apt/extended_states /root/svg_special/; dpkg --get-selections "*" > /root/svg_special/dpkg_get_selection; cp -R /etc /root/svg_special/etc

2. Ensuite il est conseillé d’utiliser screen pour pouvoir se reconnecter (avec screen -r) à en cas de déconnexion :

   screen

3. On va effectuer une mise à jour des paquets avec apt-get update && apt-get upgrade
4. Le processus de mise à niveau décrit sur le site de Debian a été conçu pour des mises à niveau des systèmes Jessie « purs » sans paquet provenant d’autres sources. Pour une meilleure fiabilité du processus de mise à niveau, vous pouvez supprimer ces paquets du système avant de commencer la mise à niveau. :

   aptitude search '~i(!~ODebian)'

5. On peut lancer la commande dpkg --audit pour s’assurer que tout est bon avant la migration. On peut également taper dpkg --get-selections "*" | more et vérifier qu’aucun paquet n’est en on hold
6. Maintenant il faut remplacer tous les “jessie” de /etc/apt/sources.list par des “stretch”, ce qui va donner chez moi :

   deb http://ftp.fr.debian.org/debian stretch main non-free
   
   deb http://debian.mirrors.ovh.net/debian/ stretch main
   deb-src http://debian.mirrors.ovh.net/debian/ stretch main
   
   deb http://security.debian.org/ stretch/updates main
   deb-src http://security.debian.org/ stretch/updates main
   

   On vérifiera aussi les autres fichiers qui peuvent se trouver dans /etc/apt/sources.list.d

7. Si vous utilisez MySQL, sachez qu’avec Stretch vous pourriez passer sur MariaDB… Si vous souhaitez utiliser MySQL, on peut se référer à ce blog post
   • On ajoute/édite le fichier source pour mysql : nano /etc/apt/sources.list.d/mysql.list
   • On y ajoute les sources suivantes (pour mysql-5.7) :

     deb http://repo.mysql.com/apt/debian/ stretch mysql-5.7
     deb-src http://repo.mysql.com/apt/debian/ stretch mysql-5.7
     

   • On ajoute la clé publique de ce repo :

     wget -O /tmp/RPM-GPG-KEY-mysql https://repo.mysql.com/RPM-GPG-KEY-mysql
     apt-key add /tmp/RPM-GPG-KEY-mysql
     rm /tmp/RPM-GPG-KEY-mysql
     

8. Il est recommandé d’utiliser le programme /usr/bin/script pour enregistrer une transcription de la session de mise à niveau. Ainsi, quand un problème survient, on a un enregistrement de ce qui s’est passé. Pour démarrer un enregistrement, taper :

   script -t 2>~/upgrade-stretch.time -a ~/upgrade-stretch.script

9. On passe aux choses sérieuses, en commençant par mettre à jour les listes des paquets :

   apt-get update

10. On va vérifier qu’on a la place suffisante (un message explicite apparait sinon) :

    apt-get -o APT::Get::Trivial-Only=true dist-upgrade

11. On va maintenant faire une mise à jour minimale :

    apt-get upgrade

12. Et à partir de là le système va vous questionner… en général choisir l’option par défaut si vous ne savez pas quoi répondre
13. Puis on continue avec

    apt-get dist-upgrade

Cette dernière étape va durer un certain temps. Une fois terminé, vous pouvez redémarrer le serveur pour s’assurer que tout va bien.

Avec phpmyadmin vous pourriez recevoir l’erreur suivante :

PHP Warning: require_once(): open_basedir restriction in effect. File(/usr/share/php/php-php-gettext/gettext.inc) is not within the allowed path(s): (/usr/share/phpmyadmin/:/etc/phpmyadmin/:/var/lib/phpmyadmin/:/usr/share/php/php-gettext/) in /usr/share/phpmyadmin/libraries/common.inc.php on line 77
PHP Warning: require_once(/usr/share/php/php-php-gettext/gettext.inc): failed to open stream: Operation not permitted in /usr/share/phpmyadmin/libraries/common.inc.php on line 77

Dans ce cas là, il faut rajouter /usr/share/php/php-php-gettext/ dans le fichier /etc/phpmyadmin/apache.conf sur la ligne open_base_dir. Ce qui va donner la ligne : php_admin_value open_basedir /usr/share/phpmyadmin/:/etc/phpmyadmin/:/var/lib/phpmyadmin/:/usr/share/php/php-gettext/:/usr/share/php/php-php-gettext/

J’ai eu quelques soucis avec fail2ban qui ne démarrait pas. J’ai pu résoudre en consultant le Troubleshooting de leur wiki. Il s’agissait du fichier /etc/fail2ban/jail.d/defaults-debian.conf qui avait été créé avec une entrée invalide. Il a suffit de le supprimer.

Une fois les erreurs corrigées, on va nettoyer tous les paquets avec

apt-get autoremove