問：小程序里面老是無法加載到系統里面的圖片，賣系統的說需要設置權限，Runtime 可寫 777Data 可寫 777Uploads 可寫 777但是我都設置了權限為完全控制了，還是不行，請問我要怎們設置才對？我應該設置哪個用戶名？Everyone的權限， IIS_IUSRS的權限，還是IUSR的權限？
,WINDOWS服務器目錄權限問題
答：您好，Everyone權限太高有安全隱患，建議可以添加一個Users用戶的寫入讀取權限試試，如還是不行的話就只有給Everyone權限，也不要設置完全控制，給讀取和寫入權限即可，非常感謝您長期對我司的支持！
問：我已經給Everyone設置了最高權限完全控制了呢！ 還是不行呢！
答：您好，
請問是否是服務器127.0.0.1上面的sqtg.yuanliw.com這個站點，您可以檢查下該服務器上是否有安裝云鎖、安全狗等防護軟件；
如需我司排查，需要登錄服務器內核實，可以選擇工單類型【主機租用vps、云主機】—【疫情期間免費】—【網站無法訪問/打開異常】提交，并附上正確的服務器登錄密碼，以及您訪問的url地址；如果是需要登錄后才能訪問對應url地址，請您也提供一個登錄測試賬號；非常感謝您長期對我司的支持!
問：服務器操作系統是centos.
答：您好，可以到西數后臺進行監控設置，如圖：，監聽對應的信息，然后設置通知，請核實
,非常感謝您長期對我司的支持!
問：200221 5:00:10 [Note] Event Scheduler: Purging the queue. 0 events200221 5:00:10 InnoDB: Starting shutdown…200221 5:00:11 InnoDB: Shutdown completed; log sequence number 5:00:11 [Note] /www/wdlinux/mysql-5.5.54/bin/mysqld: Shutdown complete
200221 5:00:42 [Note] Plugin \’FEDERATED\’ is disabled.200221 5:00:42 InnoDB: The InnoDB memory heap is disabled200221 5:00:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins200221 5:00:42 InnoDB: Compressed tables use zlib 1.2. 5:00:42 InnoDB: Initializing buffer pool, size = 128.0M200221 5:00:42 InnoDB: Completed initialization of buffer pool200221 5:00:42 InnoDB: highest supported file format is Barracuda.200221 5:00:43 InnoDB: Waiting for the background threads to start200221 5:00:44 InnoDB: 5.5.54 started; log sequence number 5:00:44 [Note] Server hostname (bind-address): \’127.0.0.1\’; port: 5:00:44 [Note] – \’127.0.0.1\’ resolves to \’127.0.0.1\’;200221 5:00:44 [Note] Server socket created on IP: \’127.0.0.1\’.200221 5:00:44 [Note] Event Scheduler: Loaded 0 events200221 5:00:44 [Note] /www/wdlinux/mysql-5.5.54/bin/mysqld: ready for connections.Version: \’5.5.54\’ socket: \’/tmp/mysql.sock\’ port: 3306 Source distribution200221 16:35:21 [Note] Plugin \’FEDERATED\’ is disabled.200221 16:35:22 InnoDB: The InnoDB memory heap is disabled200221 16:35:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins200221 16:35:22 InnoDB: Compressed tables use zlib 1.2. 16:35:25 InnoDB: Initializing buffer pool, size = 128.0M200221 16:36:02 InnoDB: Completed initialization of buffer pool200221 17:22:12 [Note] Plugin \’FEDERATED\’ is disabled.200221 17:22:12 InnoDB: The InnoDB memory heap is disabled200221 17:22:12 InnoDB: Mutexes and rw_locks use GCC atomic builtins200221 17:22:12 InnoDB: Compressed tables use zlib 1.2. 17:22:12 InnoDB: Initializing buffer pool, size = 128.0M200221 17:22:12 InnoDB: Completed initialization of buffer pool200221 17:22:12 InnoDB: highest supported file format is Barracuda.InnoDB: The log sequence number in ibdata files does not matchInnoDB: the log sequence number in the ib_logfiles!200221 17:22:12 InnoDB: Database was not shut down normally!InnoDB: Starting crash recovery.InnoDB: Reading tablespace information from the .ibd files…InnoDB: Restoring possible half-written data pages from the doublewriteInnoDB: buffer…200221 17:22:13 InnoDB: Waiting for the background threads to start200221 17:22:14 InnoDB: 5.5.54 started; log sequence number 17:22:14 [Note] Server hostname (bind-address): \’127.0.0.1\’; port: 17:22:14 [Note] – \’127.0.0.1\’ resolves to \’127.0.0.1\’;200221 17:22:14 [Note] Server socket created on IP: \’127.0.0.1\’.200221 17:22:14 [Note] Event Scheduler: Loaded 0 events200221 17:22:14 [Note] /www/wdlinux/mysql-5.5.54/bin/mysqld: ready for connections.Version: \’5.5.54\’ socket: \’/tmp/mysql.sock\’ port: 3306 Source distribution200221 17:23:57 [Warning] IP address \’127.0.0.1\’ could not be resolved: Temporary failure in name resolution2月21日下午，mysql當機了，查看了錯誤日志，沒有找到原因，請您們看一下。
答：您好，這個信息看不出具體異常原因，請查詢系統日志看下是否有存在資源不足等現象導致,非常感謝您長期對我司的支持.由此給您帶來的不便之處,敬請原諒!謝謝!
