问：小程序里面老是无法加载到系统里面的图片，卖系统的说需要设置权限，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当机了，查看了错误日志，没有找到原因，请您们看一下。
答：您好，这个信息看不出具体异常原因，请查询系统日志看下是否有存在资源不足等现象导致,非常感谢您长期对我司的支持.由此给您带来的不便之处,敬请原谅!谢谢!
